The Portkey MCP Server enables comprehensive management of AI configurations, workspaces, analytics, and user access on the Portkey platform.
User & Access Management: List, manage, and invite users to your organization. Configure user roles and access levels at both organization and workspace levels.
Analytics & Reporting: Track detailed usage analytics, including request counts, token usage, and costs. Generate filtered reports based on criteria like time range, status codes, and virtual keys.
Workspace Management: Retrieve workspace details, manage configurations, and monitor virtual keys with usage and rate limits.
Configuration & API Settings: View and manage API configurations, including cache, retry, and routing settings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Portkey MCP Server show me my API usage statistics for this month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Transform your AI assistant into a Portkey platform expert! This MCP server connects Claude to Portkey's API, enabling comprehensive management of AI configurations, workspaces, analytics, and user access.
Clone this repository
Install dependencies:
npm installCopy the example environment file:
cp .env.example .envAdd your Portkey API key to the .env file:
PORTKEY_API_KEY=your_portkey_api_key_hereThen update your Claude configuration file:
{
"mcpServers": {
"portkey-server": {
"command": "node",
"args": [
"/path/to/portkey-server/build/index.js"
],
"env": {
"PORTKEY_API_KEY": "your_portkey_api_key_here"
}
}
}
}Make sure to:
Replace /path/to/portkey-server with the actual path to your installation
Add your Portkey API key in the env section
After updating the configuration, restart Claude Desktop for the changes to take effect.
To install Portkey MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @r-huijts/portkey-admin-mcp-server --client claudeRelated MCP server: jotae-mcp
"What are my current API usage statistics across different models?"
"Show me the performance metrics for my AI deployments"
"Create a new workspace for my team's project"
"What's my current API key usage and remaining credits?"
"Generate an analytics report for last month's API calls"
"Set up rate limiting for my development environment"
"Configure fallback behavior for my production endpoints"
"Add team members to my Portkey workspace"
"Show me the latency statistics for my API calls"
"Set up custom headers for my API requests"
Variable | Description |
PORTKEY_API_KEY | Your Portkey API key (required) |
This MCP server provides comprehensive access to Portkey's platform through the following capabilities:
User Administration: List and manage all users in your Portkey organization
User Invitations: Invite new users with customizable roles and permissions
Workspace Access: Configure user access levels across different workspaces
Role-Based Control: Assign admin, manager, or member roles at organization and workspace levels
Usage Analytics: Track detailed user activity and request patterns
Cost Analysis: Monitor and analyze costs across different time periods
Request Metrics: View request counts, token usage, and response times
Filtered Reports: Generate reports based on custom criteria like status codes, virtual keys, and time ranges
Workspace Overview: List and view detailed information about all workspaces
Configuration Management: Access and review workspace configurations
Virtual Key Management: Monitor and manage API keys with usage limits and rate limits
Workspace Settings: View and track workspace metadata and user associations
Config Listings: View all available configurations in your organization
Detailed Config Info: Access cache settings, retry policies, and routing strategies
Virtual Key Details: Monitor key status, usage limits, and rate limits
API Integration: Track API endpoints and their configurations
This project is licensed under the ISC License - see the LICENSE file for details
Retrieve detailed information about a specific configuration, including cache settings, retry policies, and routing strategy
Inputs: slug (required).
Retrieve detailed cost analytics data over time, including total costs and averages per request
Inputs: time_of_generation_min (required), time_of_generation_max (required), total_units_min, total_units_max, +17 more.
Retrieve detailed analytics data about user activity within a specified time range, including request counts and costs
Inputs: time_of_generation_min (required), time_of_generation_max (required), total_units_min, total_units_max, +5 more.
Retrieve detailed information about a specific workspace, including its configuration, metadata, and user access details
Inputs: workspace_id (required).
Invite a new user to your Portkey organization with specific workspace access and API key permissions
Inputs: email (required), role (required), workspaces (required), first_name, +2 more.
List all users in your Portkey organization, including their roles and account details
Inputs: no named parameters.
Retrieve all configurations in your Portkey organization, including their status and workspace associations
Inputs: no named parameters.
Retrieve all virtual keys in your Portkey organization, including their usage limits, rate limits, and status
Inputs: no named parameters.
Retrieve all workspaces in your Portkey organization, including their configurations and metadata
Inputs: page_size, current_page.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 9 tools
Every tool has a clearly distinct purpose targeting different resources and actions, with no overlap in functionality. For example, get_config retrieves a specific configuration, list_configs lists all configurations, and invite_user handles user invitations, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_config, list_configs, and invite_user. This predictability makes it easy for agents to understand and use the tools without confusion.
With 9 tools, the server is well-scoped for managing a Portkey organization, covering configurations, users, workspaces, analytics, and keys. Each tool earns its place by addressing specific needs without being excessive or insufficient.
The toolset provides strong coverage for retrieval, listing, and user management, but lacks update or delete operations for resources like configurations or workspaces. Agents can work around this by using existing tools, but it's a minor gap in lifecycle coverage.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Connect Claude to your Platform7n workspaces: chat, links, work and decks. One-click OAuth.
Connect Claude, Cursor, or any MCP client to your FlowContent account
Manage hosts, redirects, SSL, and traffic analytics from Claude and other AI assistants.