MANUAL RUN: list codeSplitters' MCP server and OpenAPI spec in the public directories #417

The spec (/api/openapi.json) and the MCP server (/api/mcp, #396) already work for anyone who has their URLs. This is getting them listed, so people and agents can find them. Each step needs your own login.

Before any of it: merge #412 and release (zsh ~/release-codesplitters.sh, from any folder). After that, these should work:

• https://codesplitters.notryanquinn.workers.dev/mcp shows the tool list.
• https://codesplitters.notryanquinn.workers.dev/api returns JSON.

1. The official MCP Registry (registry.modelcontextprotocol.io)

Listing in the official registry is what MCP clients and other directories read from.

• Install the publisher: brew install mcp-publisher
• In a scratch folder, run mcp-publisher init, then edit the server.json it makes:
  • name: io.github.QuinnsCode/codesplitters. An io.github.* name is proved by signing in with GitHub. A name like com.yourdomain/* needs a custom domain first.
  • description: one line, e.g. "A code host where every line is its own record: read, edit, branch, merge and deploy by line."
  • Delete the packages array, since nothing is installed locally.
  • Add a remotes entry with type streamable-http and url https://codesplitters.notryanquinn.workers.dev/api/mcp. Declare that it needs an Authorization header (a cst_… token from your profile page). The exact field names depend on the schema version init writes, so check them against the registry docs.
• mcp-publisher validate
• mcp-publisher login github (your browser opens)
• mcp-publisher publish
• Check it's listed: search the registry for codesplitters.

The registry API is still v0.1. If a step's wording differs from the above, follow the registry's own docs.

2. APIs.guru (the public OpenAPI directory)

• Submit https://codesplitters.notryanquinn.workers.dev/api/openapi.json at https://apis.guru/add-api. It needs a stable URL, and they re-fetch it weekly, so later changes show up on their own.
• Their review takes a while. Close this item when codeSplitters shows up on apis.guru.

Worth knowing first

• The address: both listings use the workers.dev address. If codeSplitters moves to its own domain, update server.json and republish, and resubmit to APIs.guru.
• Sign-in: clients connect with a personal API token, not OAuth. Directories that only take OAuth servers (like the Claude connectors directory) won't accept it yet. That would need OAuth through Better Auth, the other sign-in option in codeSplitters: an MCP server on the Worker, built from the API reference #384.
• Being listed brings strangers: they can only see public repos and must sign up for a token. They count against rate limits like anyone else.

This needs you to run it, so no agent PR closes it.