Connect mcpnav directory and your agent gets 4 tools, among them get_connect_config, get_server, list_groups. It answers at https://mcp.mcpnav.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 24 September 2026; the last check, on 8 November 2026, succeeded.
Search a directory of MCP servers and get connect configs. Data is CC0/MIT-licensed.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Mirrors mcpnav.dev's own server detail page Connect block exactly (same safety rules, same comma Inputs: slug, client |
get_server | Fetch the full mcpnav record for one server by its slug (from search_servers' results, e.g. "owner/repo"). Call get_connect_config next for a ready-to-paste install snippet. Inputs: slug |
list_groups | List the category groups servers are organized into, each with its indexable server count. |
search_servers | Search the mcpnav directory of MCP servers by name/description keywords, optionally filtered to one category group. Matches are whole-word, case-insensitive, and require every query word to appear (AND); a match in the server's name ranks a Inputs: query, group, limit |
Every block below points at https://mcp.mcpnav.dev/mcp. Pick your client and copy.
claude mcp add --transport http mcpnav-directory https://mcp.mcpnav.dev/mcp
{
"mcpServers": {
"mcpnav-directory": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.mcpnav.dev/mcp"]
}
}
}{
"mcpServers": {
"mcpnav-directory": {
"url": "https://mcp.mcpnav.dev/mcp"
}
}
}{
"servers": {
"mcpnav-directory": {
"type": "http",
"url": "https://mcp.mcpnav.dev/mcp"
}
}
}{
"context_servers": {
"mcpnav-directory": {
"url": "https://mcp.mcpnav.dev/mcp"
}
}
}{
"mcpServers": {
"mcpnav-directory": {
"serverUrl": "https://mcp.mcpnav.dev/mcp"
}
}
}{
"mcpServers": {
"mcpnav-directory": {
"url": "https://mcp.mcpnav.dev/mcp"
}
}
}name: mcpnav directory
version: 0.0.1
schema: v1
mcpServers:
- name: mcpnav directory
type: streamable-http
url: https://mcp.mcpnav.dev/mcp{
"mcpServers": {
"mcpnav-directory": {
"httpUrl": "https://mcp.mcpnav.dev/mcp"
}
}
}{
"mcpServers": {
"mcpnav-directory": {
"type": "http",
"url": "https://mcp.mcpnav.dev/mcp"
}
}
}{
"mcpServers": {
"mcpnav-directory": {
"url": "https://mcp.mcpnav.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.mcpnav.dev%2Fmcp&type=streamable_http&id=mcpnav-directory&name=mcpnav%20directory
It answered our last check on 8 November 2026 in 226 ms. Over 4 checks since 24 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by mcpnav.dev and served from mcp.mcpnav.dev, the vendor's own domain: https://mcp.mcpnav.dev/mcp.
4, as returned by the server's own tools/list on 15 November 2026: get_connect_config, get_server, list_groups, search_servers.
It answered our last check on 8 November 2026 in 226 ms. Over 4 checks since 24 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.mcpnav.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.mcpnav. Endpoint host: mcp.mcpnav.dev. ARD identifier: urn:air:dev.mcpnav:mcp:directory.
First indexed 24 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.