portkey-admin

Portkey MCP Server connects Claude to Portkey's API, enabling centralized management of Portkey configurations, workspaces, analytics, and user access from within Claude Desktop. By exposing a range of capabilities—such as user administration, workspace management, usage analytics, cost analysis, and API configuration—you can perform comprehensive Portkey operations without leaving your workflow. The server provides programmatic access to Portkey features like inviting users, configuring access levels, viewing workspace metadata, monitoring API key usage, and generating detailed reports on requests, costs, and performance. With these tools, you can orchestrate team access, monitor usage, and tailor Portkey configurations to suit your organization’s governance and deployment needs.

Prerequisites:

• Node.js and npm installed on your machine
• Access to Portkey and a Portkey API key
• Claude Desktop (or your MCP runner) set up to run MCP servers

Installation steps:

1. Clone the repository to your local environment.
2. Install dependencies: npm install
3. Copy the example environment file to a real env: cp .env.example .env
4. Add your Portkey API key to the .env file: PORTKEY_API_KEY=your_portkey_api_key_here
5. Update Claude/MCP configuration to point to the server bundle, for example: { "mcpServers": { "portkey-server": { "command": "node", "args": [ "/path/to/portkey-server/build/index.js" ], "env": { "PORTKEY_API_KEY": "your_portkey_api_key_here" } } } }
6. Replace /path/to/portkey-server with the actual installation path.
7. Restart Claude Desktop (or your MCP runner) to apply the changes.

Installing via Smithery: To install Portkey MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @r-huijts/portkey-admin-mcp-server --client claude

Tips and common issues:

• Ensure PORTKEY_API_KEY is kept secret and never committed to source control.
• If the MCP server fails to start, verify that the path to /path/to/portkey-server/build/index.js is correct and that dependencies are installed.
• The environment variable mapping can be extended with additional Portkey settings if required by your organization.
• After updating configuration, always restart the Claude Desktop application to pick up new env variables and server changes.
• If using Smithery installation, ensure your network allows access to Smithery and Portkey APIs.
• Review the available capabilities (User & Access Management, Analytics & Reporting, Workspace Management, Configuration & API Settings) to plan your governance posture.