# MCPNav MCP server

> Search a directory of 20,000+ MCP servers and fetch install commands and ready-to-paste client configs.

- Listing: https://mcp.tc/i/mcpnav
- Connect: use the server's own URL `https://mcpnav.net/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: MCPNav
- Homepage: <https://mcpnav.net/>

## About

MCPNav is a searchable directory of MCP servers. Through this server an assistant can search listings by keyword and category, read a server's full record with transports and install commands, and browse categories with server counts.

It runs as a hosted streamable HTTP endpoint at https://mcpnav.net/mcp. All three tools are read-only. No sign-in or API key is needed.

## What it can do

- Search MCP servers by keyword with an optional category filter
- Get a server's description, transports and install commands
- Get a copy-paste mcpServers client config
- List directory categories with server counts and browse URLs

## Tools (3)

- `search_servers`: Search the directory by keyword with an optional category filter; returns ranked matches. (read-only)
- `get_server`: Get one server's full record, install commands and client config by slug. (read-only)
- `list_categories`: List all directory categories with server counts and browse URLs. (read-only)

## Example prompts

- "Find an MCP server for querying Postgres databases"
- "Get the install config for the GitHub MCP server"
- "List the MCP server categories and how many servers each has"
- "Search for browser automation MCP servers"

## Install

### Claude Code

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

```bash
claude mcp add --transport http mcpnav https://mcpnav.net/mcp
```

2. Start Claude Code and type `/mcp`. **mcpnav** 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 **MCPNav** and paste this URL:

```url
https://mcpnav.net/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=MCPNav&connectorUrl=https%3A%2F%2Fmcpnav.net%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcpnav.net/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://mcpnav.net/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=mcpnav&config=eyJ1cmwiOiJodHRwczovL21jcG5hdi5uZXQvbWNwIn0%3D>) (opens Cursor)

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

`mcp.json`:

```json
{
  "mcpServers": {
    "mcpnav": {
      "url": "https://mcpnav.net/mcp"
    }
  }
}
```

### VS Code

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

Or from a terminal:

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

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

`.vscode/mcp.json`:

```json
{
  "servers": {
    "mcpnav": {
      "type": "http",
      "url": "https://mcpnav.net/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`:

```json
{
  "mcpServers": {
    "mcpnav": {
      "serverUrl": "https://mcpnav.net/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

```bash
codex mcp add mcpnav --url https://mcpnav.net/mcp
```

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

`config.toml`:

```toml
[mcp_servers.mcpnav]
url = "https://mcpnav.net/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http mcpnav https://mcpnav.net/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.

```json
{
  "mcpServers": {
    "mcpnav": {
      "type": "http",
      "url": "https://mcpnav.net/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://mcpnav.net/mcp`.

## Recent changes

- 2026-11-09 02:28 UTC: Tracking started: 3 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/mcpnav#history (Atom feed: https://mcp.tc/i/mcpnav/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2025-06-18
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-11-09
- Updated: 2026-11-09

---
Source: https://mcp.tc/i/mcpnav (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
