Use mcpnav from your AI client

mcpnav also runs its own remote MCP server, so an AI agent can search this directory, look up a server, and get an install snippet without leaving the conversation.

Endpoint: https://mcp.mcpnav.dev/mcp (Streamable HTTP)

Tools

• search_servers — Search the mcpnav directory of MCP servers by name/description keywords, optionally filtered to one category group.
• get_server — Fetch the full mcpnav record for one server by its slug.
• list_groups — List the category groups servers are organized into, each with its indexable server count.
• get_connect_config — Generate a ready-to-paste install snippet for one server's first safe remote endpoint or installable package, in the requested client's format.

Connect

Add mcpnav's own server the same way you'd add any remote MCP server:

Review any command before running it. Package names and URLs come from the server's own registry entry.

claude mcp add --transport http mcpnav https://mcp.mcpnav.dev/mcp

{
  "mcpServers": {
    "mcpnav": {
      "url": "https://mcp.mcpnav.dev/mcp"
    }
  }
}

Official MCP Registry

This server is listed in the Official MCP Registry as dev.mcpnav/directory — view the Registry entry. Listing in the Registry is self-published; it does not imply endorsement by the Model Context Protocol project or Anthropic.

Limits

• Each client IP is limited to 60 requests per minute.
• Browser Origin headers are only accepted from mcpnav.dev, localhost and 127.0.0.1; non-browser clients that send no Origin header at all (the normal case for Claude Code, Cursor, curl, mcp-inspector) are allowed through.
• Request bodies over 64 KB are rejected.

Source: mcp-server/ in the mcpnav codebase. This server is not affiliated with or endorsed by the Model Context Protocol project or Anthropic.