portkey-mcp-server

@rvoh-emccaleb

About portkey-mcp-server

MCP Server for Portkey

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "portkey-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-p",
        "8080:8080",
        "\\"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is portkey-mcp-server?

This server bridges AI tools and services to Portkey through the Model Context Protocol (MCP). It is for developers who need to manage Portkey prompts—create, list, and render them—from MCP‑compatible clients like Cursor IDE and Claude Desktop.

How to use portkey-mcp-server?

Install via Docker (docker run ericmccaleb/portkey-mcp-server:latest), a pre‑built binary (make build), or from source (go run). Set the required environment variable PORTKEY_API_KEY and optionally configure transport (TRANSPORT=stdio or TRANSPORT=sse) and the SSE address (TRANSPORT_SSE_ADDRESS). Then connect using the MCP client configuration (e.g., .cursor/mcp.json or claude_desktop_config.json).

Key features of portkey-mcp-server

Exposes three Portkey prompt tools via MCP
Supports stdio and SSE transport modes
Works with Cursor IDE and Claude Desktop
Ready‑to‑use Docker image on Docker Hub
Can run as a standalone Go binary

Use cases of portkey-mcp-server

Create, render, and list Portkey prompts from an AI‑assisted IDE
Use the server as an SSE endpoint for remote prompt management
Integrate Portkey prompt operations into custom MCP‑based workflows

FAQ from portkey-mcp-server

What is the purpose of portkey-mcp-server?

It acts as a bridge, allowing MCP‑compatible tools to interact with Portkey’s prompt‑related API endpoints (create, render, list).

What transport options does it support?

It supports two transports: stdio (standard I/O, used by Claude Desktop) and sse (Server‑Sent Events, for HTTP‑based communication).

What environment variables are required?

PORTKEY_API_KEY is mandatory. Optional variables include TRANSPORT (default not specified) and TRANSPORT_SSE_ADDRESS (default :8080).

How can I run it with Docker?

Run the official image: docker run -p 8080:8080 -e TRANSPORT=sse -e TRANSPORT_SSE_ADDRESS=:8080 -e PORTKEY_API_KEY=your-api-key ericmccaleb/portkey-mcp-server:latest.

How do I integrate with Claude Desktop or Cursor?

Create a JSON configuration file (.cursor/mcp.json or claude_desktop_config.json) that specifies the Docker container or binary command with stdio transport and the PORTKEY_API_KEY environment variable.

Frequently asked questions

What is the purpose of portkey-mcp-server?

It acts as a bridge, allowing MCP‑compatible tools to interact with Portkey’s prompt‑related API endpoints (create, render, list).

What transport options does it support?

It supports two transports: `stdio` (standard I/O, used by Claude Desktop) and `sse` (Server‑Sent Events, for HTTP‑based communication).

What environment variables are required?

`PORTKEY_API_KEY` is mandatory. Optional variables include `TRANSPORT` (default not specified) and `TRANSPORT_SSE_ADDRESS` (default `:8080`).

How can I run it with Docker?

Run the official image: `docker run -p 8080:8080 -e TRANSPORT=sse -e TRANSPORT_SSE_ADDRESS=:8080 -e PORTKEY_API_KEY=your-api-key ericmccaleb/portkey-mcp-server:latest`.

How do I integrate with Claude Desktop or Cursor?

Create a JSON configuration file (`.cursor/mcp.json` or `claude_desktop_config.json`) that specifies the Docker container or binary command with `stdio` transport and the `PORTKEY_API_KEY` environment variable.