Log inSubmit server
Portkey Admin MCP logo

Portkey Admin MCP

by s-b-e-n-s-o-n

Manage Portkey AI Gateway administration through MCP tools for configs, prompts, keys, analytics, governance, and workspaces.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Portkey Admin MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "s-b-e-n-s-o-n-portkey-admin-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "portkey-admin-mcp"
      ],
      "env": {
        "PORTKEY_API_KEY": "YOUR_VALUE_HERE",
        "PORTKEY_TOOL_DOMAINS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

s-b-e-n-s-o-n/portkey-admin-mcp MCP server exposes the Portkey AI Gateway Admin API to MCP clients over a Node.js stdio process. It covers administrative areas including prompts, configs, API keys, analytics, guardrails, integrations, deployments, users, workspaces, and audit access. Set a Portkey API key, optionally limit exposed domains, and run it with npx or from a local build. Reach for it when an agent needs to inspect or change Portkey control-plane resources rather than send model requests directly.

Use cases

  • Create and revise Portkey routing configs
  • Manage workspace users, invitations, and SCIM mappings
  • Inspect Portkey cost and request analytics
  • Configure guardrails and access policies
  • Review prompts, deployments, logs, and audit records

Key features

  • Portkey Admin API access over MCP
  • Prompt, config, key, and provider administration
  • Analytics, logging, tracing, and audit tools
  • User, workspace, and SCIM management
  • Guardrails, access policies, and usage controls
  • Optional domain-based tool filtering

Tools181

What Portkey Admin MCP lets your agent do. Expand a tool for its parameters.

Verified live~73.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

18/19 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · portkey-admin-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commit10d agoMost recent push to the default branch.
Tools exposed181Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Portkey Admin MCP works

What s-b-e-n-s-o-n/portkey-admin-mcp MCP server does

s-b-e-n-s-o-n/portkey-admin-mcp MCP server exposes the Portkey Admin API as MCP tools for managing AI Gateway control-plane resources. The documented coverage spans prompts and prompt versions, routing configs, deployments, API keys, provider credentials, integrations, guardrails, access policies, limits, logs, tracing, analytics, users, workspaces, and audit data.

The server is listed in the 💻 Developer Tools category and is most relevant when an AI agent must perform operational administration through Portkey. It can support tasks such as creating or revising a gateway config, reviewing config versions, managing workspace membership, handling invitations, inspecting usage analytics, and applying governance settings. Destructive operations are available for resources such as users, workspaces, configs, and pending invitations, so client workflows should request confirmation where appropriate.

How it works

s-b-e-n-s-o-n/portkey-admin-mcp MCP server runs as a Node.js MCP process and authenticates requests with a Portkey API key. The client discovers the available tools and invokes the corresponding Portkey Admin API operations. Most operations require suitable API-key scopes; a 403 with Portkey error AB03 indicates missing permissions rather than an unavailable endpoint.

Tool exposure can be narrowed with PORTKEY_TOOL_DOMAINS, using values such as prompts,analytics. Domain filtering is useful when a client only needs a subset of the catalog and when reducing tool-list context is important.

Setup and configuration

Install and run the package through npx:

bash
PORTKEY_API_KEY=your_key npx -y portkey-admin-mcp

For a focused tool set, add PORTKEY_TOOL_DOMAINS:

bash
PORTKEY_API_KEY=your_key \
PORTKEY_TOOL_DOMAINS=prompts,analytics \
npx -y portkey-admin-mcp

Claude Code can register the process with claude mcp add. Cursor, Windsurf, and VS Code use their respective MCP JSON configuration files, with npx as the command and PORTKEY_API_KEY in the environment.

Tools and capabilities

The available administration areas include:

  • Create, version, render, execute, migrate, and promote prompts.
  • Create and revise routing, caching, retry, load-balancing, and target settings in configs.
  • Manage API keys, virtual keys, providers, secret references, and external integrations.
  • Configure guardrails, access policies, egress allowlists, usage limits, and rate limits.
  • Review cost, latency, error, token, cache, provider, MCP, A2A, and workspace analytics.
  • Manage users, invitations, workspaces, members, and SCIM group mappings.
  • Retrieve logs, work with traces, inspect deployments, and access audit records.

Config updates create new versions rather than overwriting prior versions. Workspace and organization operations use distinct tools, and several enterprise administration and analytics operations require an Enterprise Portkey plan.

Limitations and notes

s-b-e-n-s-o-n/portkey-admin-mcp MCP server targets the Portkey-compatible Admin API and uses the x-portkey-api-key authentication model. It is not a direct Prisma AIRS or Strata Cloud Manager integration, and changing the base URL alone is not described as a supported migration path.

Access depends on both the Portkey plan and the scopes assigned to the API key. Enterprise-gated tools return 403 on non-Enterprise plans. Deleting a workspace or config is permanent according to the tool descriptions, while deleting a workspace member does not delete the organization user. Check identifiers and permissions before invoking mutating tools.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Portkey Admin MCP

s-b-e-n-s-o-n/portkey-admin-mcp is an MCP server that connects MCP clients to the Portkey AI Gateway Admin API. Its tools manage prompts, configs, API keys, analytics, guardrails, integrations, deployments, users, workspaces, logging, and governance resources through a Portkey API key.

Run it with npx using a Portkey API key: `PORTKEY_API_KEY=your_key npx -y portkey-admin-mcp`. You can also add the command to Claude Code, Cursor, Windsurf, or VS Code MCP configuration, or build the repository and run its generated `build/index.js` file.

Yes, it works with Cursor through an MCP configuration file. Add `npx` as the command, `-y portkey-admin-mcp` as the arguments, and set `PORTKEY_API_KEY` in the server environment.

Set `PORTKEY_TOOL_DOMAINS` to a comma-separated selection such as `prompts,analytics`. The server then exposes a focused subset of domains, which can reduce the amount of tool-list context a client must process.

It needs a Portkey API key with scopes appropriate to the tools being called. Most tools use a workspace-scoped service key with the required permissions, while some organization-level operations are restricted to Portkey Enterprise plans.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPortkey Admin MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/s-b-e-n-s-o-n-portkey-admin-mcp?style=directory)](https://allmcps.com/mcp/s-b-e-n-s-o-n-portkey-admin-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/s-b-e-n-s-o-n-portkey-admin-mcp"><img src="https://allmcps.com/api/badge/s-b-e-n-s-o-n-portkey-admin-mcp?style=directory" alt="Portkey Admin MCP on AllMCPs" /></a>