Skip to content

Add a setup page for every server and client combination - #59

Merged
lbesecker195 merged 1 commit into
mainfrom
feat/server-agent-pages
Sep 24, 2026
Merged

lbesecker195 merged 1 commit into
mainfrom
feat/server-agent-pages

Conversation

@lbesecker195

Copy link
Copy Markdown
Owner

Closes #58.

/servers/:namespace/:name/for/:agent — one page per listing per client. H1 is SERVER for CLIENT, as requested.

Clients added, each verified against vendor docs

Client Where it reads from Shape
Cline cline_mcp_settings.json in the editor's globalStorage mcpServers
Gemini CLI ~/.gemini/settings.json mcpServers, httpUrl for remote
Grok .mcp.json — Grok Build reads Claude Code's file unchanged mcpServers + type
ChatGPT Settings → Connectors → Developer mode remote URL, UI only
Claude.ai Settings → Connectors → Add custom connector remote URL, UI only
LangChain not a config file langchain-mcp-adapters Python

ChatGPT and Claude.ai appear only for remote listings — neither runs a packaged server, so for a stdio listing there is genuinely nothing to show, and inventing a config would be worse than omitting the page.

Five names deliberately have no page

GPTBot and BingBot are crawlers. Chrome Lighthouse audits page performance. Perplexity publishes an MCP server rather than consuming other people's. Aider has no native MCP support — only a community bridge.

A page telling a reader to install this server in Lighthouse would rank for a question it answers falsely. That costs more than the traffic is worth, on a domain whose value is being the reliable answer.

One deviation from the spec, flagged

The requested title was How to install SERVER MCP Server — set up guide for SERVER tutorial, naming the server twice. That gives all twelve pages for a listing an identical <title> — duplicate titles across ~400,000 pages, and nothing in the SERP telling a searcher which result matches their client. The title now names the client instead of repeating the server:

How to install Weather MCP Server in Cursor — setup guide and tutorial

Say the word and I'll revert to the literal wording.

143 tests pass, including one asserting the five non-clients get no page.


Pages affected:

🤖 Generated with Claude Code

/servers/:namespace/:name/for/:agent answers "how do I install <server> in
<client>" at the listing level. H1 is "SERVER for CLIENT".

- Add Cline, Gemini CLI, Grok, ChatGPT, Claude.ai and LangChain to the client
  registry, each with its own verified shape: globalStorage JSON for Cline,
  httpUrl for Gemini, Claude Code's own .mcp.json for Grok, a connectors UI
  flow for ChatGPT and Claude.ai, and Python for LangChain
- Show ChatGPT and Claude.ai only for remote listings, since neither runs a
  packaged server and there would be nothing honest to show
- Carry the live secret injector onto these pages too
- Chunk the agent URLs into their own sitemap files, 3,000 listings each

The title names the client as well as the server. The requested wording named
the server twice, which would have given all twelve pages for a listing the
same title -- duplicate titles across 400,000 pages, and nothing to tell a
searcher which result answers their client.

GPTBot, BingBot, Chrome Lighthouse, Perplexity and Aider get no page. The first
three crawl or audit, Perplexity publishes a server rather than consuming
others, and Aider has no native MCP support. A setup guide for any of them
would rank for a question it answers falsely.

---

Pages affected:

- [MCP Registry](https://ai.mcpharbor.dev/) — the Model Context Protocol server directory.
- [Browse MCP servers](https://ai.mcpharbor.dev/servers) — the catalogue these hang off.
- [Brave Search MCP](https://ai.mcpharbor.dev/servers/com.brave/brave-search) — a listing with setup guides per client.
- [Sitemap](https://ai.mcpharbor.dev/sitemap.xml) — now carries the agent files.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@lbesecker195
lbesecker195 merged commit b6695f3 into main Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a setup page for every server and client combination

1 participant