servers VS inspector

Most agents don't speak raw HTTP — they speak MCP. So the real distribution surface is a tiny MCP server that exposes each endpoint as a tool and does the paying under the hood. The agent calls web_search(query); the server hits the paid endpoint, handles the 402 with its operator's wallet, returns JSON. One line to install:

The Model Context Protocol (MCP) is an open standard for connecting AI hosts (Claude, ChatGPT, Cursor, VS Code, and others) to external context and actions through a structured protocol instead of ad-hoc plugins.

Model Context Protocol specification

That changed when I built mpesa-mcp — a Model Context Protocol server that wraps the Daraja API and makes it directly available to Claude, GPT-4, and Gemini.

If you haven't run into it yet, MCP (Model Context Protocol) is an open standard for exposing tools to AI agents. two-go ships an MCP server that runs over stdio with no dependencies, no URL, no account, and no API key. It's all local.

MCP server surface. The CLI is already agent-friendly, so I'm double minded about whether a Model Context Protocol server would make integration smoother. I'm personally not a fan of MCP and prefer skills and CLIs.

As noted in the Model Context Protocol (MCP) Introduction, this protocol allows Claude to interact with systems like GitHub and local databases through a standardized interface.

Keep the project's living context: current task state, decisions, conventions, known footguns as plain Markdown committed to the repo, and expose it to the agent over MCP.

The MCP ecosystem doubles every few months. Bookmark the official MCP servers repository for the canonical list.

To test the Gateway, you'll need to use a client that supports CIMD. That rules out the MCP Inspector. Fortunately, both VS Code and Claude Code do, hosting their CIMDs here and here respectively. Let's use VS Code.

GitHub：modelcontextprotocol/inspector — 9,774 Stars，1,308 Forks

Sim. O inspector MCP oficial se comunica diretamente via stdio e oferece uma UI para testes manuais.

# 1. Discover the auth server curl http://localhost:3000/.well-known/oauth-protected-resource # 2. Register a client curl -X POST http://localhost:3000/register \ -H "Content-Type: application/json" \ -d '{"redirect_uris":["http://localhost:3334/callback"]}' # 3. Walk the auth code flow # The MCP Inspector from Anthropic does this end to end: # https://github.com/modelcontextprotocol/inspector

This behavior appears in modelcontextprotocol/inspector #293, where connecting caused repeated server starts, and modelcontextprotocol/inspector #723, where reconnect logic did not preserve enough state to resume safely. The lesson is simple: retries are part of system design, not a bandage you slap on at the edge. If your retry policy is not explicit, you do not really have one.

Since I’m currently learning it too, I want to share how to build your first MCP server using MCP Framework. After that, we’ll test it with MCP Inspector, then finally add it to an MCP host — in this case, Copilot.

MCP Inspector (GitHub): testing and debugging tool for MCP servers

Before connecting Flowise, we must verify our server. Since we are using SSE, we can use the MCP Inspector web interface to connect to our running server.

First, there's the specification that defines how clients and servers should talk to each other. Then you've got SDKs in different languages that handle the protocol details for you. The MCP Inspector helps you test and debug your servers during development. And finally, there are reference server implementations you can learn from or use directly.