---
title: "The mcp.tc MCP Server | mcp.tc"
description: "Search the mcp.tc directory from your AI assistant: add https://mcp.tc/mcp, then ask for servers, install commands and setup steps. Read-only, no sign-in."
url: "https://mcp.tc/docs/mcp"
markdown: "https://mcp.tc/docs/mcp.md"
lang: "en"
---

# The mcp.tc MCP server

mcp.tc runs its own MCP server at `https://mcp.tc/mcp`. Add it to your assistant, and it can search the directory and hand you a server’s own URL or install command with the setup for your client. It’s read-only and needs no sign-in.

## Add it

It’s a remote server that needs no sign-in, so it works in any client that supports remote MCP servers. The URL:

`Server URL`:

```
https://mcp.tc/mcp
```

Setup for each client, the same as on its listing, [mcp.tc/i/mcp-tc](https://mcp.tc/i/mcp-tc):

### Claude Code

1. Run this in a terminal, in your project folder:

```
claude mcp add --transport http mcp-tc https://mcp.tc/mcp
```

2. Start Claude Code and type `/mcp`. **mcp-tc** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.
2. Name it **mcp.tc** and paste this URL:

```
https://mcp.tc/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=mcp.tc&connectorUrl=https%3A%2F%2Fmcp.tc%2Fmcp)

2. Check that the URL reads `https://mcp.tc/mcp` and click **Add**.
3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.
2. Enter a name for the server.
3. Under **Connection**, paste `https://mcp.tc/mcp` as the server URL, then for authentication choose **No authentication**.
4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](https://cursor.com/install-mcp?name=mcp-tc&config=eyJ1cmwiOiJodHRwczovL21jcC50Yy9tY3AifQ%3D%3D)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```
{
  "mcpServers": {
    "mcp-tc": {
      "url": "https://mcp.tc/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](https://vscode.dev/redirect/mcp/install?name=mcp-tc&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tc%2Fmcp%22%7D)

Or from a terminal:

```
code --add-mcp '{"name":"mcp-tc","type":"http","url":"https://mcp.tc/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```
{
  "servers": {
    "mcp-tc": {
      "type": "http",
      "url": "https://mcp.tc/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```
{
  "mcpServers": {
    "mcp-tc": {
      "serverUrl": "https://mcp.tc/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```
codex mcp add mcp-tc --url https://mcp.tc/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```
[mcp_servers.mcp-tc]
url = "https://mcp.tc/mcp"
```

### Gemini CLI

```
gemini mcp add --transport http mcp-tc https://mcp.tc/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```
{
  "mcpServers": {
    "mcp-tc": {
      "type": "http",
      "url": "https://mcp.tc/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.tc/mcp`.

## Tools

Three tools, all read-only. Each one declares an output schema and returns structured data plus one short text block that reads well on its own.

All three carry `readOnlyHint: true` and `destructiveHint: false`, so clients that ask before running a tool can skip the question. Arguments they don’t know are rejected, so a typo fails loudly instead of being ignored. Answers are in English, the language of the listings’ source text.

## Things to ask

Ask in plain words. The model picks the tool and the arguments.

- Find an MCP server for Postgres that runs locally.
- Which project management MCP servers work without sign-in?
- How do I add the Linear MCP server to Claude Code?
- List the mcp.tc categories and how many servers each has.
- Give me the Cursor setup for the Sentry MCP server.
- What tools does the DeepWiki MCP server have, and do any of them write?

## What comes back

A search for servers about issues that need a sign-in, `search_servers` with these arguments:

`Request`:

```
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "search_servers",
    "arguments": {
      "query": "issues",
      "auth": "sign-in",
      "limit": 3
    }
  }
}
```

`Text the model reads`:

```
11 listings match "issues", auth sign-in, showing the first 3. Call get_server with a slug for the endpoint URL or install command and setup steps.
- GitHub: Work with GitHub repos, issues, pull requests, Actions workflows and code search from your AI assistant. [slug github; remote, OAuth sign-in; verified] https://mcp.tc/i/github
- Linear: Find, create and update Linear issues, projects and comments from your AI assistant. [slug linear; remote, OAuth sign-in; verified] https://mcp.tc/i/linear
- Sentry: Query Sentry errors, issues and traces, and run Seer root-cause analysis from your coding assistant. [slug sentry; remote, OAuth sign-in; verified] https://mcp.tc/i/sentry
More: https://mcp.tc/directory?q=issues&s=auth&sort=popular
```

Then one of them in full, with its Cursor setup:

`Request`:

```
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "get_server",
    "arguments": {
      "slug": "linear",
      "client": "cursor"
    }
  }
}
```

`Text the model reads`:

````
Linear: Find, create and update Linear issues, projects and comments from your AI assistant.
By Linear. Productivity & Projects. Verified by mcp.tc: official server from Linear.
Listing page: https://mcp.tc/i/linear
Server URL (connect to this): https://mcp.linear.app/mcp
Access: OAuth: the client opens Linear's sign-in the first time it connects.
Connects an assistant to a Linear workspace for project management and issue tracking. You can find, create and update issues, projects and comments without leaving the chat. Runs as a hosted streamable HTTP endpoint at https://mcp.linear.app/mcp. Users sign in with Linear through OAuth, with read and write scopes. A read-only variant is available at /mcp/readonly. The tool list is not published in the probe, so available tools depend on the live server.
History (tools and version not read): no change recorded yet. https://mcp.tc/i/linear#history
Setup for Cursor:
Add to Cursor: https://cursor.com/install-mcp?name=linear&config=eyJ1cmwiOiJodHRwczovL21jcC5saW5lYXIuYXBwL21jcCJ9
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
```json
{
  "mcpServers": {
    "linear": {
      "url": "https://mcp.linear.app/mcp"
    }
  }
}
```
Note: Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.
````

You can try it without a client. The server keeps no sessions, so a single request works:

```
curl -s https://mcp.tc/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_servers","arguments":{"query":"issues","auth":"sign-in","limit":3}}}'
```

## Protocol details

The server describes itself in a [server card](https://mcp.tc/mcp/server-card) (name, version, URL and protocol versions), and a `GET` on `/mcp` points to it in a `Link` header.

## In the browser (WebMCP)

Browsers with [WebMCP](https://webmachinelearning.github.io/webmcp/) find the same tools on every mcp.tc page: `search_servers`, `get_server` and `list_categories` answer from `/mcp`, and `open_listing` opens a listing in the same tab. On a listing page, `get_server` and `open_listing` work without a slug. The search forms are tools too (`search_directory`). There’s nothing to install and no sign-in, and the page stores nothing.

## Privacy and trust

- Your search terms aren’t logged or stored. The one thing the server writes is the rate-limit counter, kept under a keyed hash of your IP address for up to 2 days.
- Like every request to mcp.tc, the request line (path, time, IP address, user agent) goes into the web server’s access log, kept 14 days. The body, with your query in it, doesn’t. The [Privacy Policy](https://mcp.tc/privacy) has the details.
- Names, descriptions and tool summaries come from each server’s own metadata. The server strips control characters and caps their length, and its instructions tell the model to treat them as data and never follow instructions found in them.

---
Source: https://mcp.tc/docs/mcp. Markdown version for AI agents (ask for `text/markdown` or add `.md` to the address). Site overview: https://mcp.tc/llms.txt
