Smithery registry

Smithery is a directory for MCP servers. Cowpin’s listing:

Current status (automated smoke)

Run from the cowpin-web repo:

node scripts/smithery-registry-smoke.mjs
# or: npm run qa:smithery

Check	Expected today
Smithery page	200 — listing exists
GitHub `cowpin-ai/mcp-server`	Public — canonical open-source MCP (SDK-based stdio server)
npm `@cowpin/mcp-server`	404 until published — blocks `npx -y @cowpin/mcp-server` and Smithery’s default install

So: Smithery was attempted earlier (listing + smithery.json in cowpin-ai/mcp-server). Install may still fail until npm publish completes.

Repo	Role
github.com/cowpin-ai/mcp-server	Official MCP SDK server; Smithery metadata (`smithery.json`) lives here
cowpin.com	Product web & API endpoints (`/api/agent/mcp` + `/mcp-bridge.mjs`)

After changing smithery.json, commit to cowpin-ai/mcp-server and re-sync the listing on Smithery if their UI requires it.

Publish npm — GitHub secret NPM_TOKEN + workflow publish-mcp-server.yml in cowpin-web, or npm publish --access public from cowpin-ai/mcp-server (see docs/agent-discovery-runbook.md in the monorepo).
Use curl bridge (no npm) — Connect Cowpin to Cursor → install script → node ~/.local/share/cowpin/mcp-bridge.mjs.

Smithery CLI (after npm exists):

npx -y @smithery/cli install @cowpin/mcp-server --client cursor

npm view @cowpin/mcp-server version returns a version
Smithery listing “Install” succeeds with a test cw_agent_… key
smithery.json on GitHub matches Smithery dashboard (homepage → connect-cursor doc)
Blog links point at cowpin-ai/mcp-server for OSS star; product docs point at connect-cursor