AGT-10 · MCP servers & tool interoperability¶
Each project wraps the same client systems as custom tools for one agent, so nothing is reused and every copilot surface needs its own integration. MCP servers that do exist are hand-rolled, have unclear auth and break when the protocol or SDK moves, as it did with the stateless 2026-07-28 revision and Python SDK v2.
- Who reads it: Agent engineers building tools, platform engineers hosting them and DevOps engineers operating MCP servers
- Outcome: Tools built once, catalogued and safely consumable by every agent
- Pack owner: Sivaraj (catalog owner role: Agent Lead)
Master catalog entry¶
- Catalog name: MCP & Tool Interoperability Standard (P2)
- Why it matters: Positions the practice ahead on the emerging tool-integration standard
- What it removes: Tools built once are consumable by every agent and copilot surface
- Stack: Model Context Protocol, Python SDK, Azure hosting
- Maturity target: Level 2 — server template plus internal tool catalog
Playbooks¶
| ID | Story | Title | Kind | Complexity | Urgency | Status | Owner | Planned publish |
|---|---|---|---|---|---|---|---|---|
| PB-AGT-10-01 | AGT-10-S1 | Build an MCP server from the Orion Python template | How-to | Medium | 3 | draft | Sandeep Velu | 2026-12-15 |
| PB-AGT-10-02 | AGT-10-S2 | Choose how to host and expose MCP servers on Azure | Decision guide | Medium | 3 | draft | Sivaraj | 2026-11-30 |
| PB-AGT-10-03 | AGT-10-S3 | Rotate MCP server credentials without breaking agents | Runbook | Medium | 5 | draft | Sivaraj | 2026-11-05 |
| PB-AGT-10-04 | AGT-10-S4 | Upgrade an MCP server to a new protocol revision or SDK major version | Runbook | High | 4 | draft | Sivaraj | 2026-11-27 |
| PB-AGT-10-05 | AGT-10-S5 | Publish a tool server to the internal MCP catalog | Checklist | Low | 3 | draft | Sandeep Velu | 2026-12-03 |