What this is
Tool focus: Model Context Protocol
Design Model Context Protocol (MCP) servers and integrations for agentic AI: tool surface, scopes, secrets, transport choice and review patterns.

MCP lets agents call your tools. Good MCP design is API design for a model caller.
The tool surface is the interface — designed for the model that calls it.
What this is
Design Model Context Protocol (MCP) servers and integrations for agentic AI: tool surface, scopes, secrets, transport choice and review patterns.
Expose the few tools the model can call accurately, with clear names, arguments and failure modes.
Authentication, per-user scopes, secret storage and agent-host identity are designed before the server is useful.
stdio, HTTP or SSE is chosen deliberately, with notes on what would justify changing it later.
Week 1
Tool inventory
Which internal tools exist, which the agent should reach, what the existing API surface already does, and what new shape the MCP server needs.
Week 2
Design and skeleton
Tool naming, argument schema, scopes, transport and error model. First tools go live in a skeleton server.
Week 3
Real integration
Codex, Claude Code or an internal agent calls the server on real tasks. Logs shape the tool surface.
Both, depending on the tool. Off-the-shelf servers exist for common things and there is no point reimplementing them. Custom servers are worth it when the tool is specifically yours: an internal API, a domain-specific search, a private dataset.
stdio for local single-developer integration, HTTP for shared internal services, SSE where the tool produces a stream the agent should react to. The choice is decided early because changing it later is expensive.
The MCP server should look like any other API to the identity layer: it is a client of the same SSO, it respects the same scopes, and its calls show up in the same audit trail. The agent does not get a parallel identity universe.