Guides
MCP integration
Connect ASMP discovery to MCP tool surfaces.
ASMP and MCP compose. ASMP declares what exists. MCP invokes tools on it.
Layer separation
| Layer | ASMP | MCP |
|---|---|---|
| Question | What services exist? | What tools can I call? |
| Discovery | GET /capabilities | Tool list from MCP server |
| Invocation | Endpoint in manifest | call_tool(name, args) |
Registry MCP tools (today)
The reference implementation exposes these MCP tools:
| Tool | Description |
|---|---|
service_list | List all registered services with health |
service_find | Find by capability or search query |
service_health | Check health of one or all services |
service_register | Register a new service |
MCP bridge (planned)
Auto-generate MCP tool manifests from ASMP service capabilities:
Service declares: provides: [email.classify, email.search]
→ MCP bridge exposes: email_classify(), email_search()
→ Other agents discover via ASMP, invoke via MCPBidirectional: an MCP server can register itself via ASMP on startup.
Example: compose both
1. Agent needs email classification
2. service_find(capability="email.classify") → director-daemon on :7400
3. Agent connects to director-daemon MCP server
4. Agent calls email classification tools directlyASMP is step 2. Without it, step 2 is filesystem archaeology.