Full Portkey Admin API MCP server — configs, prompts, keys, analytics, and more.
Connect Portkey to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Full Portkey Admin API MCP server — configs, prompts, keys, analytics, and more. The portkey mcp server is what makes that connection.
You need a Portkey API key with appropriate scopes. Get one from your Portkey dashboard under API Keys.
Because 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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Area — ToolsAudit — list_audit_logsConfiguration — Production containers must choose their rate-limit topology explicitly: set RATE_LIMIT_STORE=redis for multi-instance deployments, or setConfiguration is passed through the environment: PORTKEY_API_KEY, PORTKEY_BASE_URL, MCP_PUBLIC_BASE_URL, MCP_AUTH_TOKEN, PORTKEY_ALLOW_PRIVATE_BASE_URL, MCP_REDIS_URL, MCP_EVENT_ENCRYPTION_KEY, MCP_TLS_KEY_PATH. 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.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Portkey's toolset — Area, Audit, Configuration — is a fair guide to whether it matches your workflow. It is maintained by CodesWhat; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Area | Tools |
| Audit | list_audit_logs |
| Configuration | Production containers must choose their rate-limit topology explicitly: set RATE_LIMIT_STORE=redis for multi-instance deployments, or set RATE_LIMIT_SINGLE_PROCESS=true only for a single long-lived process. |
Then use this config:
```json
{
"mcpServers": {
"portkey-admin": {
"command": "node",
"args": ["/path/to/portkey-admin-mcp/build/index.js"],
"env": {
"PORTKEY_API_KEY": "your_api_key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PORTKEY_API_KEY | Credential the server authenticates with. | Yes |
| PORTKEY_BASE_URL | Credential the server authenticates with. | Yes |
| MCP_PUBLIC_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| PORTKEY_ALLOW_PRIVATE_BASE_URL | Credential the server authenticates with. | Yes |
| MCP_REDIS_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_EVENT_ENCRYPTION_KEY | Credential the server authenticates with. | Yes |
| MCP_TLS_KEY_PATH | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.