← Docs

MCP North as an MCP server

The directory itself is an MCP server. Point any MCP-compatible AI agent at our endpoint and it can search the catalog, read server details, and fetch install guides on its own.

Endpoint

https://mcpnorth.com/mcp

Transport: Streamable HTTP (POST). No authentication required.

Connect from Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcp-north": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcpnorth.com/mcp"]
    }
  }
}

This uses mcp-remote to bridge the HTTP endpoint into Claude Desktop.

Available tools

  • search_servers — search by keyword, with relevance ranking. Args: query (required), category (optional), limit (1–20, default 5).
  • get_server — full details for one server. Args: slug (e.g. "github-mcp").
  • list_categories — all categories with server counts.
  • get_related — servers related to a given one. Args: slug, limit.
  • get_install_guide — install command, client compatibility, and links. Args: slug.

Example

An agent helping a user who needs GitHub automation could:

  1. Call search_servers with query: "github pull requests".
  2. Call get_install_guide with the top result's slug.
  3. Walk the user through the install command.

Try it

Send a POST to https://mcpnorth.com/mcp with an MCP initialize payload, or just open /mcp in your browser to see the server info.