Namespaced tool composition
Combine pinned MCP server definitions with explicit namespaces, aliases, and retained upstream provenance.
Composition plane
Build one MCP from the servers you already run.
Compose pinned MCP server definitions behind one stable endpoint today; richer schema diff, promotion, and collision workflows remain on the roadmap.
Product boundary
Composer is a working preview for namespaced, version-pinned tool composition. Cross-target import, full protocol objects, and release promotion still require end-to-end proof.
- Available now
- Behavior backed by the current local vertical slice and automated tests.
- Preview
- Useful implementation exists, but the complete operating journey is not proven.
- Planned
- Part of the open MCP-native roadmap, not current product behavior.
- Deployment
- Managed cloud and self-hosted targets share portable packages; live parity remains an acceptance test.
Capabilities
What composer controls
Status labels distinguish tested behavior from useful previews and the open roadmap.
Portable configuration export
Export tenant configuration without secrets; live import from managed cloud to Kubernetes remains unproven.
Stable endpoint
Publish a scoped endpoint whose namespaced tool surface can combine builtin and remote HTTP members.
Schema-aware promotion
Compare tool, resource, and prompt schemas before promoting or rolling back an immutable release.
Operating flow
The target journey, with current maturity called out above.
Register
Import remote URLs, stdio packages, containers, or OpenAPI definitions.
Compose
Select capabilities, establish namespaces, and resolve collisions.
Publish
Release a versioned endpoint with policy, identity, and health attached.
Target control surface
Designed for platform and security teams.
These controls define the intended product boundary; the capability labels above are the current implementation record.
- Immutable composition versions
- Capability-level aliases
- Environment promotion
- Rollback to a known release
- Portable configuration export
- Upstream schema diff
Evaluate locally or inspect either deployment target.
The managed cloud and Kubernetes paths are previews of one open codebase, with no intended capability gate or mandatory call-home path.