Need to Prevent MCP Sprawl
Multiple teams are independently building MCP integrations for the same third-party services without coordination or visibility.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Laura, the head of AI, discovered multiple teams are independently building MCP integrations for the same third-party services without coordination.
Problem Context
- Multiple teams pilot GitHub MCP integrations without knowing others are doing the same
- “None of those teams are talking to each other”
- Need to register MCP servers somewhere, but “we have an API catalog—it’s similar but different”
Problem Impact
- Duplicated engineering effort across teams
- Inconsistent implementations of the same MCP capabilities
- No way to consolidate learnings from parallel pilots
Naftiko Today
- MCP exposure with Streamable HTTP and stdio transports provides a single, standardized way to build MCP servers, preventing teams from rolling their own incompatible implementations
- Backstage Integration (Fleet) offers a centralized catalog where MCP capabilities can be registered and discovered, giving teams visibility into what already exists
- Executable YAML specs mean teams can share and reuse MCP capability definitions without writing code, eliminating duplicated engineering effort
- CLI wizard (
naftiko create capability) and VS Code Extension provide a governed creation path that guides teams toward the shared catalog instead of building in isolation
Naftiko Tomorrow
- Naftiko Shipyard MVP (Fleet Second Alpha) would provide a dedicated MCP capability registry where teams discover existing integrations before building new ones
- Starter templates (Second Alpha) would offer pre-built MCP capability specs for common services like GitHub, Jira, and Slack, eliminating the most common sources of duplication
- OpenAPI-to-Naftiko import (Second Alpha) would let teams quickly convert existing API integrations into shared MCP capabilities rather than building from scratch
- Fabric capability discovery (v1.1) would enable enterprise-wide search across all registered MCP capabilities, making sprawl immediately visible