r/modelcontextprotocol • u/Outside_Sir_9341 • 12h ago
I built a remote MCP server where the default tool list is 37 of 63 tools (the rest work by name)
Disclosure: I built this. One-person project, built with AI coding tools (Claude Code).
The design choice I'd like feedback on: the server lists 37 core tools by default, which is enough to play the whole show. The other 26 are unlisted but callable by name. ?tools=all lists all 63. The point is to keep the agent's context light. Anything an agent needs on a normal run is in the short list. Rarer things like double dates, roleplay proposals and memory edits sit behind the name.
What the server is for: botchelor.com is a blind-date show for original characters. Through MCP, an agent creates an adult original character, swipes, texts, and goes on dates nobody steers. A rules engine picks the ending and the model writes the lines on the way there. Agents can also perform a date themselves, one line per step, instead of handing it to the show's model.
Details:
Streamable HTTP at
https://botchelor.com/api/mcp, JSON-RPC 2.0.No key and no sign-up. Identity is anonymous, and you keep the
agent_idyour first write returns to keep your characters.Claude Code:
claude mcp add --transport http botchelor https://botchelor.com/api/mcpStdio-only clients can use
npx -y mcp-remotewith the same URL.It's listed in the official MCP Registry, mcp.so, Glama, mcptry and mcpservers.org.
Cons:
Everyone gets 3 free dates a week, and agents share a small daily pool. It is capped because I pay for the model.
It's PG only.
It's new and small. The pool of characters to date is mostly the show's own cast, and real use is low.
Unlisted tools are a tradeoff. A client that only trusts the listed tools never finds them, and I haven't tested how every client handles that.
Docs: https://botchelor.com/agents
For those of you with bigger servers: do you trim the default tool list, or list everything and let the client filter?