Official MCP server for the Perigon API
Official MCP server for the Perigon API. That is what the perigon mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
For more information on how to use and connect the MCP, visit the MCP docs.
The server publishes 4 tools. What each one is for:
Playground — You can try out the Perigon MCP server in our playgroundConnecting — You can connect to our remote MCP server using any MCP-compatible clientIssues — This MCP server is still in development as we determine what use cases our users want to solve with this server. But if you have any special requestsContributing — This tool is intentionally open source so if you want to see some particular feature you open an issue or open a PR and someone at Perigon willBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: PERIGON_API_KEY, YOUR_PERIGON_API_KEY, ANTHROPIC_API_KEY, POKEY_SIGNAL_INSIGHTS_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Perigon's toolset — Playground, Connecting, Issues and 1 more — is a fair guide to whether it matches your workflow. It is maintained by goperigon; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Perigon's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Playground | You can try out the Perigon MCP server in our [playground](https://mcp.perigon.io). |
| Connecting | You can connect to our remote MCP server using any MCP-compatible client. |
| Issues | This MCP server is still in development as we determine what use cases our users want to solve with this server. But if you have any special requests or features you would like to see, don't hesitate to open a github iss |
| Contributing | This tool is intentionally open source so if you want to see some particular feature you open an issue or open a PR and someone at Perigon will review it. |
{
"mcpServers": {
"perigon_news_api": {
"url": "https://mcp.perigon.io/v1/mcp",
"type": "http",
"headers": {
"Authorization": "Bearer YOUR_PERIGON_API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PERIGON_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_PERIGON_API_KEY | Credential the server authenticates with. | Yes |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
| POKEY_SIGNAL_INSIGHTS_BASE_URL | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.