Portkey MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Portkey MCP Server?

Portkey MCP Server is a management server that connects Claude to Portkey's API, allowing users to manage AI configurations, workspaces, analytics, and user access effectively.

how to use Portkey MCP Server?

To use the Portkey MCP Server, clone the repository, install dependencies, configure your environment with your Portkey API key, and restart Claude Desktop. Alternatively, you can install it automatically via Smithery.

key features of Portkey MCP Server?

  • User and access management for Portkey organization
  • Detailed analytics and reporting on API usage
  • Comprehensive workspace management capabilities
  • Configuration and API settings management

use cases of Portkey MCP Server?

  1. Monitoring API usage statistics across different models.
  2. Generating performance metrics for AI deployments.
  3. Creating and managing workspaces for team projects.
  4. Analyzing costs and usage patterns over time.
  5. Configuring user roles and permissions within the organization.

FAQ from Portkey MCP Server?

  • How do I install the Portkey MCP Server?

You can install it from source or via Smithery using the provided commands.

  • What is required to run the server?

You need a valid Portkey API key and the necessary environment configurations.

  • Can I manage multiple workspaces?

Yes! The server allows you to manage multiple workspaces and their configurations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago