MCP Servers
Model Context Protocol
Open protocol for connecting agents to tools and context.
Best when multiple agent clients should discover and call the same tool surface without bespoke integrations.
Use MCP as a capability boundary, not as a reason to expose every internal API to agents.
Best for
- tool interoperability
- context resources
- remote servers
Not ideal for
- single-app tool calls with no reuse need
- unsafe tools without authorization boundaries
Core concepts
clientsserverstoolsresources
Minimal implementation shape
Wrap one narrow tool in an MCP server, add auth, log calls, then connect it to one agent client before expanding the surface.