Odd Bits / Builder kits
MCP Connector Kit
If you have an API and want people to use it from Claude, this is a small working starter. It handles the parts that take the first days: checking the OAuth token on each request, tool definitions written to Anthropic’s published review criteria, and a checklist of what the directory asks for. Plain TypeScript. You can read all of it in an afternoon, then replace the example tools with your own.
- What you get
- A remote MCP server starter with OAuth checks and a test suite
- A tool linter and a dated submission checklist
- Plain TypeScript you can read in an afternoon
- Works with
- Node 22.6+TypeScriptClaude connectors
- Version
- v1.0, updated 2026-10-19
Email for an invoice: $9.99Paid by invoice for now. Files arrive by email once it clears.
How you get it: email me. I send a USD invoice through Wise; when it clears, the files come by email as a zip, within one working day. A hosted checkout may replace the invoice later.
What's inside
- A remote MCP server (tools only), as one request-to-response function: the MCP endpoint, the protected-resource metadata and a health check
- OAuth resource-server checks: audience, issuer, expiry and scopes, and the 401 and 403 responses Claude’s client expects
- A local-only demo authorization server, so you can run the whole sign-in flow on your laptop. It is never for production
- Four example tools, written to Anthropic’s review criteria, for you to replace
- A tool linter (npm run check-tools) built from Anthropic’s published review criteria
- A test suite (npm test)
- SUBMISSION-CHECKLIST.md: every rule has a source link and the date it was checked (2026-10-19). It lists what you hand over in the developer portal: a test account, a privacy policy URL, docs, listing text and the compliance acknowledgments
- AUTH.md: putting a real identity provider in front. DEPLOY.md: notes for running it somewhere public
- It answers both protocol eras: the 2026-07-28 stateless one and the older initialize handshake
- TypeScript, Node 22.6 or newer, no build step
What was checked
- The official MCP TypeScript SDK client (1.32.1), including its own OAuth flow, passes against the server.
- The MCP Inspector command line listed the tools and called two of them. This was checked by hand once.
- A fresh unzip, npm ci and npm test pass.
- Six deliberate security breakages each make the test suite fail.
- Run on Node 24 only.
What was not checked
- Claude itself (claude.ai, Desktop, Claude Code) has not been run against this code by us. Anthropic asks you to test your server in Claude before you submit, and the checklist says how.
- A modern-era (2026-07-28) client. The official SDK speaks the older era, so the modern behaviour is tested with hand-written requests that follow the spec pages.
- Any real identity provider, and any hosting platform. Only Node is tested.
- Load, or more than one server instance. The rate limiter and store are in memory.
- Tools only: no resources, prompts, streaming or subscriptions.
Who it's for
Developers who already have an API and want to build the connector themselves, and who are fine reading TypeScript.
What it never does
- Promise your connector will be listed, approved or reviewed by any date. Anthropic decides. The checklist records what Anthropic’s published pages said on 2026-10-19
- Host anything. You run the server and answer for your users’ data
- Replace a security review of your server. Read the spec’s security section and Anthropic’s expectations before going live
- Send anything anywhere on its own
- Claim to be affiliated with or endorsed by Anthropic
Questions
Will this get me listed?
No promise. The checklist tells you what Anthropic’s pages asked for on 2026-10-19, and you submit yourself.
What if the rules change?
Every rule has a source and a date. The README says how to update the checklist. Check Anthropic’s current pages before you submit.
Can I use the demo sign-in in production?
No. It is for local testing only. AUTH.md explains using a real identity provider.
Which Node version?
22.6 or newer. It runs the TypeScript directly, with no build step.
Can I use it for client projects?
Yes. Use and modify it for your own and your clients’ projects. Don’t resell or republish the kit.
Is the free MCP Inspector enough?
For trying a server, often yes. This kit adds the OAuth checks, the linter and the checklist.
Why are four example tools in there?
They show the habits the checklist asks for: separate read and write tools, a title and annotations on each, and errors that say how to fix the problem.
Not affiliated with or endorsed by Anthropic. Anthropic and Claude are named only to say what this works with.