We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Docs

Everything about using mcp.tc, building on it and getting your server listed.

What mcp.tc is

mcp.tc is a directory of Model Context Protocol servers: 1,547 of them right now, in 20 categories. Some are hosted services that your AI app reaches over HTTPS. Others are programs it starts on your own computer.

Every listing gets a link built from the server’s name, such as mcp.tc/i/notion. The page behind it says what the server does, lists its tools, says whether it needs a sign-in or an API key, and shows how to add it to each client. Its History tab records what changed and when.

Nothing you add goes through mcp.tc. The buttons, commands and config snippets all use the server’s own URL or package, so once you add a server, your client talks to it directly. Your tool calls, sign-in tokens and API keys never reach us. The mcp.tc link is the server’s page, not its address. If you paste it into a client by mistake, the client gets an error that names the server’s own URL or install command (details).

Quick start

  1. Find the server

    Search the directory by name, vendor or topic, or filter it by what a server needs: No sign-in, Sign-in or API key, or Runs locally. You can also guess the address: mcp.tc/i/ plus the name. Spelling is forgiving, so mcp.tc/i/huggingface opens hugging-face and mcp.tc/i/github-mcp opens github.

  2. Open its page

    The box at the top shows what to paste: the server’s own URL for a hosted server, or the install command for a local one. The first badge under the name says what it needs: No sign-in, OAuth sign-in, Needs an API key, Sign-in optional or Runs locally.

  3. Add it in one click

    Add to Claude Code copies a terminal command. Add to Cursor, Add to VS Code and Add to claude.ai open that client’s own install page with the server filled in, for the clients that can use it. The Set up section has steps for up to nine clients, plus a config that works in most others. If the server needs a sign-in, your client opens the vendor’s sign-in page.

  4. Share it

    Copy the mcp.tc link under Share this server. Whoever opens it gets the same page, with the setup for their own client.

For example, mcp.tc/i/deepwiki gives you DeepWiki’s own URL, https://mcp.deepwiki.com/mcp, and this command for Claude Code:

claude mcp add --transport http deepwiki https://mcp.deepwiki.com/mcp

In these docs

Elsewhere on the site, Recent changes lists the latest changes across the directory, Badges and embeds has every embed option, Verified checkmark explains the checkmark and how to get one, and About covers how listings are checked and who runs mcp.tc.

Words used on the site

Remote server
Hosted by its vendor. Your client connects to its URL over HTTPS, and there’s nothing to install.
Local server
A program your client starts on your computer with an install command, such as npx -y @modelcontextprotocol/server-memory.
No sign-in, Sign-in, Local
What a server needs, shown as a badge with a colored dot: green for no account or key, amber for an OAuth sign-in or an API key at the vendor, gray for a server that runs on your computer.
The server’s own URL
The address the vendor runs the server at, such as https://mcp.deepwiki.com/mcp. This is what your client connects to.
The mcp.tc link (quick link)
https://mcp.tc/i/{name}, the listing’s page. You share it, and it opens the page with the setup steps.
Verified
The checkmark after a name means we confirmed who runs the server (163 listings have it). It isn’t a security review.
History
A tab on each listing that records what our checks found changing, and when: tools added, removed or changed, and new versions. It shows what our own checks saw and isn’t a security review. Edits by the server’s owner appear there too.
Follow
Sign in and follow a listing to get an email when its History records a change.