Using MCP Harbor

Using MCP Harbor

Finding a server

Browse MCP servers searches names, titles, descriptions, tags and the names of the tools each server exposes, so a query like create_issue finds servers by what they can do, not only by what they are called. Filter by transport (stdio, streamable-http, sse). There is no browsing by tag: too few listings carry tags for a tag page to be useful, though search still matches them.

Every card shows the server's logo — see where logos come from — and how many tools it has.

A server's page

Each listing, for example Context7, has:

• Install instructions for each client, in that client's own format. They differ more than people expect: VS Code reads servers, not mcpServers; Zed reads context_servers; Windsurf calls a remote URL serverUrl. A snippet copied from the wrong client silently does nothing.
• A secrets box. Paste an API key and it is filled into the snippet in your browser. It is never stored, logged or sent anywhere.
• The server's server.json, as published.
• Its tools, prompts and resources, read from the live server where it can be reached.
• A changelog link once anything about it has changed.

The pages under a server

Path	What it answers
/servers/<name>/for/<client>	"How do I install this server in Cursor / Claude Code / VS Code…?"
/servers/<name>/tools and /tools/<tool>	What each tool does, and how to call it from each client
/servers/<name>/prompts	Prompts — things you invoke, such as a slash command in Claude Code
/servers/<name>/resources	Resources — data a client attaches as context
/servers/<name>/changelog	What changed, and when — see Changelogs

These pages exist only where there is something to put on them. A server with no prompts has no prompts page rather than an empty one.

Tools, prompts and resources are different things

• A tool is something the model calls on its own.
• A prompt is something the user invokes deliberately; the client will not call it for you.
• A resource is data — a file, a page, an API response — that the client attaches as context.

Most servers expose tools only. Of the remote servers that answer, roughly one in ten offers prompts and one in six offers resources.

Clients covered

Claude Code, Claude Desktop, Claude.ai, ChatGPT, Cursor, VS Code, Windsurf, Zed, Cline, Gemini CLI, Grok and LangChain. ChatGPT and Claude.ai only appear for remote servers, because neither runs a packaged server locally.

Crawlers and tools that are sometimes asked for — GPTBot, Bingbot, Lighthouse — do not get pages: they do not run MCP servers, and a guide claiming they do would be wrong.