MCP Server Kit · $5 · for coding agents
Your agent builds the MCP server. This kit tells it what broke when I built mine.
21 real cases from building, testing and publishing worklore's own MCP server: what failed, what fixed it, and a check for each. You put the folder next to your project, and your coding agent opens the case that matches its task before it writes the code.
One payment, no subscription. Every future version included. 30-day refund.
Checkout opens here as soon as payments are switched on. Until then, write to sales@worklore.dev and I'll send you the kit.
Why a note for the agent helps
I test this. In worklore's round 11 (345 runs), Claude Haiku without a note solved 1 of 15 tasks that had a hidden trap. With a short note about the trap it solved 15 of 15. Claude Opus, a much stronger model, solved 7 of 15 without the note. The runs and the grading scripts are public.
Those tasks were not about MCP servers. A round on building an MCP server with and without this kit comes next, and its numbers will be on this page, whatever they are.
The kit carries what the docs don't say: the client that throws where your test passed,
the listing that calls a server read-only when it can write, the registry token that needs
read:org. If the docs already say it, your agent has it, and a kit adds nothing.
What's inside
Five folders, in the order you build a server. Every case is also free to read on worklore.dev; the kit is the same text in one folder, with an index that tells the agent which case to open.
1. Design the server and its tools
- An MCP server for the price of one more endpoint
- One table decides what answers without a token: how I stopped re-deciding auth tool by tool
- My MCP server hid its own tool list behind a login
- Cut Claude Code token cost 4×: let your MCP tool take a URL instead of the pasted file
- My MCP listing said read-only. My server could write.
2. Sign users in
- An MCP server that signs users in: OAuth 2.1 on AWS Lambda, start to token
- App review wants test credentials, but my app only had Google sign-in
3. Test it the way real clients use it
- My tests passed because they agreed with me
- My live MCP test asserted the bug: a real client threw where my test passed
- Check your MCP server in a few minutes: the failures real clients hit in the sample
- My MCP server's output schemas accepted wrong answers: 7 of 8 tools in the sample
- I sent every write tool of my two servers a second time, and 8 of 31 duplicated or hit the wrong record
- A canary read back from the log store found the one field my masker skipped
- Benchmark your MCP server in Claude Code, Codex and Gemini: one fake server, its call log as the judge
- Cloudflare's security-audit skill in Claude Code: 5 real bugs in my MCP server in 15 minutes
4. Document and measure it
- A pre-commit hook that regenerates your README from the code
- Your MCP server is one URL: getting per-tool, per-user analytics anyway
5. Publish it where people find it
- Getting into the MCP Registry: server.json, a read:org token, and why listed is not discoverable in the sample
- Submitting an MCP server to the directories: one CLI, one GitHub issue, three traps
- Everything you write before you can submit an MCP server for review
- Submitting to the Claude connectors directory: no Team plan needed, and the auth option that would break it
How it works
- Pay once. Checkout is run by Paddle. The download link arrives by email.
- Unzip the folder into your project, or anywhere your agent can read.
- Add one line to
AGENTS.mdorCLAUDE.md:Before building or changing the MCP server, read ./worklore-mcp-server-kit/START-HERE.md and use the cases that match the task.
The folder is plain Markdown in the Open Knowledge Format
(OKF v0.2): an index.md in every folder so the agent reads only what it needs, and a
log.md with the changes. It works with Claude Code, Codex, Cursor, Gemini CLI and any
agent that can read files. Nothing runs, nothing is installed, and no account is needed.
Updates
When a new MCP case is published on worklore, it goes into the kit. You get an email with the new version, and your download link always gives the latest one. No extra charge.
Questions
- Why pay if every case is free on worklore.dev?
- You're paying for the folder: the cases picked and sorted by building stage, an index your agent can follow, offline use, and the updates. If you'd rather point your agent at the website, that works too, and I won't mind.
- Who wrote it?
- Me, Valentina Koniukhova. I built and run worklore's MCP server, which is listed in the official MCP Registry. Every case comes from that work, including the failures.
- Can I share it with my team?
- Use it in your own projects and your team's. Please don't republish the folder itself.
- What if it doesn't help?
- Ask for a refund within 30 days of buying, for any reason. See the refund policy.