MCP server

MCP Reference ServersProtocols

The clearest way to understand the Model Context Protocol is to read servers that implement it correctly, and this is that collection. Useful both as working connectors and as the template to copy when writing your own.

Context7Protocols

Ask for a library by name and Context7 resolves it to an identifier like /vercel/next.js, then answers queries with version-specific snippets from a continuously re-indexed documentation corpus — so the model writes against the API that exists today rather than the one in its training data. Setup is one command or a URL pasted into any MCP client, and anyone can submit a public repository to the index. Know what you are adopting: the open-source part is a thin client, while the crawler, parser and index are Upstash's private hosted service — the free tier stops at 1,000 calls a month, and when the hosted endpoint went down for a stretch in August 2026, the tool had nothing to answer from.

chrome-devtools-mcpProtocols

It hands an agent a live Chrome plus the instruments of DevTools: it records a performance trace and reads out Core Web Vitals with named insights, lists network requests and source-mapped console errors, runs Lighthouse audits, and still clicks and fills forms from a text snapshot of the page the way browser MCPs do. It can attach to the Chrome you already have open, profile and all — which is also where care is needed. The trade against Playwright MCP is scope: this is Chrome-only, and what that buys is analysis no cross-browser server offers.

playwright-mcpComputer Use

Playwright MCP puts a real Chrome, Firefox, WebKit or Edge behind an MCP server and returns each page as an accessibility snapshot: a text outline of roles, names and reference ids that the agent clicks and types into, with no vision model and no coordinate guessing. Past plain navigation it can mock network requests, read and write cookies and web storage, record a trace or a video, and emit Playwright locators and assertions, which makes it a practical way to turn a session you drove by hand into a test you can check in. The cost is context: Microsoft's own README points coding agents at the Playwright CLI with skills instead, because the tool definitions and the snapshots compete for the same window as your codebase. It earns its keep in long-running loops, where holding one browser open across many turns is worth paying that.

github-mcp-serverProtocols

Point Claude, Copilot, Cursor or any other MCP client at it and the model can triage an issue, open and review a pull request, search code it has never downloaded, and read the logs of a failed Actions run — all through the GitHub API, so nothing is cloned. The remote server GitHub hosts needs no local setup or runtime at all; the same local server runs as a container or a single binary, and is the only route for GitHub Enterprise Server. The trade-off is breadth: more than eighty tools sit across twenty-odd toolsets, and only five toolsets are on by default for good reason — turning everything on gives most models more choices than they handle well.

Blender MCPTools & Integrations

Blender is powerful and its learning curve is the reason most people never get past a cube. This bridges it to any MCP-capable assistant: an add-on inside Blender opens a connection, and from the other side the model can create and move objects, apply materials, inspect the scene and run Python against Blender's own API. That last part is the important detail and the main risk — the assistant is not limited to a fixed set of operations, so it can do things you did not anticipate in a file you care about. Installation is genuinely three steps, but they span two programs: a package runner, an MCP client entry, and an add-on enabled inside Blender itself.

AWS MCP ServersProtocols

Point Claude, Cursor, Kiro or any other MCP client at one of these servers and the model can search current AWS documentation, write CloudFormation and CDK against AWS's own guidance, query DynamoDB or PostgreSQL, read CloudWatch logs and estimate costs — each capability is its own small server, started with one uvx command and your AWS credentials. Two need no setup at all: the hosted Knowledge server answers documentation questions without an AWS account, and the preview AWS MCP Server reaches the AWS APIs under IAM permissions with CloudTrail logging. The open question is longevity: AWS announced the Agent Toolkit for AWS in May 2026 as this suite's successor, recommends it for production agent work, and says the most useful servers here will move into it over time.

XcodeBuildMCPTools & Integrations

A coding agent working on an iOS project can write Swift all day and never find out whether it compiles, because the commands that would tell it are long, particular and easy to get subtly wrong. This exposes them properly: build a scheme, boot a simulator, install and launch the app, read the logs, run the tests. Because the agent gets a result it can act on, the loop closes — it fixes the error it just caused instead of handing you a diff to try. It ships as both an MCP server and a plain command-line tool, with optional skills that tell the agent how to use whichever one you installed. It is macOS-only and tracks a current Xcode.