Portkey MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORTKEY_API_KEY | Yes | Your Portkey API key (required) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_all_usersB | List all users in your Portkey organization, including their roles and account details |
| invite_userB | Invite a new user to your Portkey organization with specific workspace access and API key permissions |
| get_user_statsC | Retrieve detailed analytics data about user activity within a specified time range, including request counts and costs |
| list_workspacesA | Retrieve all workspaces in your Portkey organization, including their configurations and metadata |
| get_workspaceA | Retrieve detailed information about a specific workspace, including its configuration, metadata, and user access details |
| list_configsB | Retrieve all configurations in your Portkey organization, including their status and workspace associations |
| list_virtual_keysB | Retrieve all virtual keys in your Portkey organization, including their usage limits, rate limits, and status |
| get_cost_analyticsC | Retrieve detailed cost analytics data over time, including total costs and averages per request |
| get_configC | Retrieve detailed information about a specific configuration, including cache settings, retry policies, and routing strategy |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.