typescript-sdk VS specification

Model Context Protocol Documentation - Complete MCP reference Typescript SDK

View on GitHub

For TypeScript you can refer to https://github.com/modelcontextprotocol/typescript-sdk/blob/...

There isn't much documentation available right now but you can ask coding agent eg. Claude Code to generate an example.

@modelcontextprotocol/sdk: MCP server framework

At the time of this writing, this is little more than a proof of concept as a combination of the starter Pulsar package-generator package, the Atom package creation tutorial and the example from the official MCP Typescript SDK with some editor tool functions registered. Hopefully it will become more soon, since I am looking forward to actually using it to build stuff!

MCP TypeScript SDK

For this, we're going to use McpServer from the modelcontextprotocol SDK. The SDK supports: Resources, Tools, Prompts. However for this demo we'll only need tools.

Building a custom MCP server is straightforward with the right tools. While servers can be written in any language supporting stdout, official SDKs simplify the process. The TypeScript SDK is a great starting point.

For me it was implementing a simple `execute_terminal_command` tool along with hooking up to my company's jira and gitlab (dont worry security gurus, for the command line, I have a hardcoded list of allowed read-only commands that the LLM can execute, and both jira and gitlab servers likewise have readonly options.

What I will say is I agree there should be an option to get rid of the chat confirmations of every single new tool call in a chat - as well as building a set of "profiles" of different tools depending what I'm working on. Also strongly agree there needs to be an internal prompt possibility to explicitely tell the LLM what tool(s) to favor and how to use them (even in addition to the descriptions / schemas of the tools themselves) I opened an issue on the anthropic repo exactly about this: https://github.com/modelcontextprotocol/typescript-sdk/issue...

No. Any file that runs MCP Server is fine anywhere. I am intending a workspace separate from the rails app. The MCP server should be run in a separate process from the rails app. At least until the streamable http transport is ready.

https://github.com/modelcontextprotocol/specification/pull/2...

Another aspect worth noting is that, to date, the protocol requires a persistent connection between client and server, so this can be a drawback for auto-scalable architectures that adapt to demand, as well as moving in the opposite direction in a world that is striving to become stateless.

The MCP protocol is evolving with proposals like the new Streamable HTTP transport that supports fully stateless servers without requiring long-lived connections. We're following these developments closely and evaluating how they might benefit the Supabase MCP experience.

I assume they're (for now at least) targeting the old HTTP+SSE version of MCP, and not the new Streaming HTTP version? https://github.com/modelcontextprotocol/specification/pull/2...

Really looking forward to integrating with these models.

The next version of Model Context Protocol will have native audio support (https://github.com/modelcontextprotocol/specification/pull/9...), which will open up plenty of opportunities for interop.

Yup. Though it's a JSON API and not an XML API like SOAP. As for how it differs form the old OpenAPI/Swaggar... shrug... not much... its got a lot less flexibility to it and it has specific tooling for agentic tool use.

https://github.com/modelcontextprotocol/specification/blob/m...

Hey Taylor! One of the creators of emcee here.

So... short answer... there isn't a great way right now. Currently emcee is communicating over stdio – and although MCP technically supports SSE, it isn't super friendly to remote workflows.

You can see it's definitely on the roadmap for MCP here, however: https://github.com/modelcontextprotocol/specification/discus...

Curious to hear how you were thinking of using emcee remotely? Feel free to email me at [email protected] too.

We've been keeping a close on this topic: https://github.com/modelcontextprotocol/specification/discus...

The options being considered to do this are: