SDK MCP Server vs MCP Server
People think every MCP server is a separate program you start and connect to. An SDK MCP server is not, because it runs inside your own app. Its tools are plain functions in your code. A normal MCP server runs on its own, as a local process or a remote service. Use the SDK kind for tools that call your own code, and a normal one to share tools across apps.
SDK MCP Server
An MCP server that runs in your own app. Its tools are plain functions in your code.
An SDK MCP server is an MCP server that runs inside your own app, made with createSdkMcpServer(). Its tools are plain functions in your code. So they can reach your database and your data with no extra process and no network hop. If a handler throws an error, the server turns it into an error result. Claude reads it, and the loop goes on.
MCP Server
A program that gives AI apps tools, data or prompts through MCP.
An MCP server is a program that offers tools, data or prompts to AI apps through MCP. It often wraps a service you already have, like a file system, a database or a web app. When a client asks, the server says what it offers. Then it answers requests. A server can run on the same computer as the app or on a remote machine. Thousands of servers exist, and many are open source.
In one line
- SDK MCP Server
- An MCP server that runs in your own app. Its tools are plain functions in your code.
- MCP Server
- A program that gives AI apps tools, data or prompts through MCP.