Aggregate multiple MCP backends behind a single stdio endpoint with namespaced routing.
{
"mcpServers": {
"io-github-oaslananka-composer": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Aggregate multiple MCP backends behind a single stdio endpoint with namespaced routing.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
🌱 Agricultural AI: Soil analysis, crop recommendations, weather forecasts. FREE TurboQuant.
Hierarchical markdown memory palace for AI agents — structured palace navigation via MCP tools.
Bounding box(bbox) GIS tool: coords conversion, EPSG, WKT, GeoJSON, H3, Overpass, POI, map viz
I Ching hexagram analysis and geographic feng shui for Taiwan locations
MCP Security Weekly
Get CVE alerts and security updates for io.github.oaslananka/composer and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The missing infrastructure layer for Model Context Protocol ecosystems.
flowchart LR
Shared["@oaslananka/shared"]
Forge["@oaslananka/forge"]
Sentinel["@oaslananka/sentinel"]
Atlas["@oaslananka/atlas"]
Composer["@oaslananka/composer"]
Bridge["@oaslananka/bridge"]
Observatory["@oaslananka/observatory"]
Lab["@oaslananka/lab"]
Shared --> Forge
Shared --> Sentinel
Shared --> Atlas
Shared --> Composer
Shared --> Bridge
Shared --> Observatory
Shared --> Lab
Clients["IDE / Agent / SDK clients"] --> Sentinel
Clients --> Composer
Composer --> Backends["Backend MCP servers"]
Sentinel --> Backends
Forge --> Composer
Forge --> Sentinel
Atlas --> Clients
Observatory --> Sentinel
Observatory --> Forge
Lab --> Composer
Most MCP projects stop at the server boundary. mcp-suite focuses on the harder production layer around it: transport compatibility, trust boundaries, orchestration, discovery, observability, and operator workflows. That makes it useful once you move past a single local demo and start running MCP in teams, CI, or internal platforms.
The suite is Azure-first by design. Azure DevOps Pipelines are the primary CI/CD path, GitHub remains the mirror and release host, and every package is prepared for public npm publishing under the @oaslananka scope. The monorepo stays strict TypeScript, Turborepo, pnpm, and Changesets based.
Compared with one-off MCP utilities, the packages here are designed to compose: shared defines the protocol/runtime baseline, sentinel and composer control traffic, forge orchestrates work, atlas catalogs capability, bridge generates servers, observatory closes the feedback loop, and lab gives contributors a desktop workbench.
| Package | What it does | Docs |
| ------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------- |
| @oaslananka/shared | Shared MCP protocol, transports, auth, retry, telemetry, and testing primitives | Shared docs |
| @oaslananka/forge | Pipeline engine for orchestrating MCP tools and external steps | Forge docs |
| @oaslananka/sentinel | Zero-trust security proxy with audit, approval, and PII controls | Sentinel docs |
| @oaslananka/atlas | Registry API and catalog UI for discovering MCP servers | Atlas docs |
| @oaslananka/composer | Aggregation proxy for multiple backend MCP servers | Composer docs |
| @oaslananka/bridge | OpenAPI and schema-first MCP server generation | Bridge docs |
| @oaslananka/observatory | Metrics, traces, anomaly detection, alerting, and dashboard UI