Skip to main content

4 posts tagged with "mcp"

View All Tags

What I learned building partner-center-mcp

· 8 min read

Building against the Partner Center REST API means living in Microsoft Learn. Microsoft archived the Partner Center .NET SDK in June 2023 and points partners at the REST APIs, but the SDK still turns up in search results, and so does code that requests tokens for the retired graph.windows.net audience and gets a 401 with error 900420 back. A model trained on that material reproduces it with confidence.

partner-center-mcp is the MCP server I wrote to put the current documentation next to the agent instead. This post is about the decisions behind it, and what I would tell anyone designing an MCP server.

Designing tools an LLM can use correctly

· 8 min read

When you give a model a tool, you are publishing an API. The consumer is an unusual one, though. It never reads your source, never opens the documentation site, and never asks a colleague what a parameter means. All it gets is a name, a paragraph of description and a JSON Schema, and from those it has to decide whether to call the tool, when, and with what.

Everything I believe about API design still applies. The difference is that the margin for ambiguity is gone: a developer who misreads a parameter finds out in code review, a model finds out in production, if at all.

What the Model Context Protocol actually standardises

· 8 min read

Every AI application wants to reach the same things: the repository, the issue tracker, a database, the documentation. Before the Model Context Protocol, each of those connections was written once per application. An integration built for one editor was useless in the next one.

MCP is the agreement that lets one integration work in every application that speaks it. It is much smaller than the noise around it suggests, and that is the best thing about it. This post is about what it actually pins down, checked against the current specification, revision 2026-07-28.

Why I built Derbent

· 5 min read

I use more than one coding agent on the same repositories. Claude Code works on one thing, Codex on another, and now and then I ask Copilot CLI something. Each of them is good at its job, and none of them knows what the others did.