Perigon MCP server

The official Perigon MCP server.

Documentation

For more information on how to use and connect the MCP, visit the MCP docs.

Maintainers

The Perigon MCP Server is developed and maintained by the Perigon engineering team.

Lead Developer: Islem Maboud, responsible for the architecture, implementation, and ongoing development of this MCP server, including the remote transport layer, authentication handling, deployment configuration, and the MCP playground.

Usage

MCP Registry

The official MCP Registry name for this server is io.github.goperigon/perigon-mcp-server. server.json is the source of truth for that listing. A published registry version is immutable, so any change to the listing requires bumping version in server.json and publishing again.

Playground

You can try out the Perigon MCP server in our playground.

Note: A valid Perigon API key is required to use the MCP. The MCP playground requires you to be already authenticated to the Perigon dashboard.

Connecting

You can connect to our remote MCP server using any MCP-compatible client.

Server URL: https://mcp.perigon.io

The recommended transport is Streamable HTTP (/v1/mcp). SSE (/v1/sse) is supported for legacy clients but not recommended for new integrations.

Quick Setup Examples

Streamable HTTP — native support (recommended):

{
  "mcpServers": {
    "perigon_news_api": {
      "url": "https://mcp.perigon.io/v1/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_PERIGON_API_KEY"
      }
    }
  }
}

Streamable HTTP — via mcp-remote (for clients without native HTTP support):

{
  "mcpServers": {
    "perigon_news_api": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://mcp.perigon.io/v1/mcp",
        "--header",
        "Authorization: Bearer ${PERIGON_API_KEY}"
      ],
      "env": {
        "PERIGON_API_KEY": "YOUR_PERIGON_API_KEY"
      }
    }
  }
}

For Claude Code (CLI):

claude mcp add --transport http perigon_news_api https://mcp.perigon.io/v1/mcp \
  --header "Authorization: Bearer YOUR_PERIGON_API_KEY"

SSE (legacy clients only):

{
  "mcpServers": {
    "perigon_news_api": {
      "url": "https://mcp.perigon.io/v1/sse",
      "type": "sse",
      "headers": {
        "Authorization": "Bearer YOUR_PERIGON_API_KEY"
      }
    }
  }
}

📖 For detailed setup instructions for different clients, see our comprehensive MCP documentation.

Selecting specific tools

With no ?tools= filter, a session gets searchnewsarticles, the five stats tools, the monitor read tools (including setmonitorstatus), getapiaccess, every Signal Insights tool, and the search tools your API key's scopes allow. Several large tools stay off that default and must be requested by name or profile: createmonitor, updatemonitor, getsourcebyid, gettoptopics, getstory_stats, and the watchlist, source-group, contact-point, and article-refresh tools. You can also restrict a session to a smaller set with ?tools=. This is useful for reducing context size and keeping the model focused.

https://mcp.perigon.io/v1/mcp?tools=search_news_articles,search_news_stories

Shortened. The full README is on GitHub.