Aggregates multiple MCP backends into a single namespaced proxy endpoint. It manages backend connections, routes tools by namespace, and handles name conflicts across servers.
From the registry: Aggregate multiple MCP backends behind a single stdio endpoint with namespaced routing.
$ npm install -g @oaslananka/composerPlease install the `composer-oaslananka` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install MCP Composer globally with npm** — Install the Composer CLI package so the `composer` command is available. Run: `npm install -g @oaslananka/composer`
Canonical MCP server config (stdio transport):
- command: `composer`
- args: ["serve","--config","<path-to-composer-config.yml>"]
Note: Composer runs as a local stdio MCP server and proxies to multiple backend MCP servers defined in a YAML config file. You must create a composer config file listing upstream servers, for example with `transport: http` and `url: <your-backend-mcp-url>` entries.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.