Portkey MCP Server for Cline 10 tools — connect in under 2 minutes
Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Portkey through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Portkey and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"portkey": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Portkey MCP Server
What you can do
Connect AI agents to the Portkey AI Gateway for enterprise-grade observability and management:
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Portkey tool calls without waiting for prompts between steps. Connect 10 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- Monitor logs and traces of all LLM calls passing through your gateway
- Analyze token usage, latency, and costs across models and teams
- Submit feedback (Likes/Dislikes) to improve model quality and agent performance
- Export logs for audit trails, compliance, and offline cost analysis
- Review gateway configurations including retry policies, fallbacks, and cache settings
- Manage virtual keys to track provider API key usage and limits
- Discover supported models from 1,600+ LLMs available via Portkey
- Enforce budget policies to prevent runaway AI costs per team or project
The Portkey MCP Server exposes 10 tools through the Vinkius. Connect it to Cline in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Portkey to Cline via MCP
Follow these steps to integrate the Portkey MCP Server with Cline.
Open Cline MCP Settings
Click the MCP Servers icon in the Cline sidebar panel
Add remote server
Click "Add MCP Server" and paste the configuration above
Enable the server
Toggle the server switch to ON
Start using Portkey
Ask Cline: "Using Portkey, help me...". 10 tools available
Why Use Cline with the Portkey MCP Server
Cline provides unique advantages when paired with Portkey through the Model Context Protocol.
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Portkey + Cline Use Cases
Practical scenarios where Cline combined with the Portkey MCP Server delivers measurable value.
Autonomous feature building: tell Cline to fetch data from Portkey and scaffold a complete module with types, handlers, and tests
Codebase refactoring: use Portkey tools to validate live data while Cline restructures your code to match updated schemas
Automated testing: Cline fetches real responses from Portkey and generates snapshot tests or mocks based on actual payloads
Incident response: query Portkey for real-time status and let Cline generate hotfix patches based on the findings
Portkey MCP Tools for Cline (10)
These 10 tools become available when you connect Portkey to Cline via MCP:
create_policy
Requires policy name, budget limit (USD or token count), and optionally the target users or virtual keys to restrict. Returns the created policy details. Use this to enforce cost controls on specific teams or projects using the gateway. Create a new budget or usage policy for AI gateway access
delete_policy
Requires the policy ID. Use this when a project ends or budget constraints are no longer needed. Remove a budget or usage policy from Portkey
export_logs
Optionally filters by date range, model, or user. Returns an export ID or download URL. Use this for audit trails, cost reporting, or offline analysis of AI usage patterns. Export AI gateway logs for external analysis or compliance reporting
get_log_details
Requires the log ID from list_logs results. Use this for deep debugging of specific AI interactions. Get detailed information about a specific AI gateway log entry
get_virtual_keys
Virtual keys map to underlying provider keys (OpenAI, Anthropic, etc.) with metadata, usage limits, and policy associations. Returns key IDs, names, provider targets, current usage, and status. Use this to audit API key usage or identify keys approaching limits. List all virtual API keys managed by Portkey
list_configs
Returns config IDs, names, creation dates, and associated virtual keys. Use this to review how LLM requests are routed or to audit gateway behavior. List all gateway configurations stored in Portkey
list_logs
Returns log IDs, timestamps, model names, token usage, latency, costs, and status codes. Use this to monitor AI usage, identify expensive calls, or debug latency issues. Supports pagination via limit/offset. List recent AI gateway logs and traces from Portkey
list_models
). Returns model names, provider names, supported endpoints (chat, embeddings, etc.), and capabilities. Use this to discover which models are routable via your gateway. List all LLM models supported by the Portkey gateway
list_policies
Returns policy names, limits, current consumption, and affected users/keys. Use this to review guardrails preventing runaway AI costs. List all budget and usage policies defined in Portkey
submit_feedback
Requires the log ID, rating (LIKE, DISLIKE, or UNLIKE to remove), and optional text feedback. Use this to build RLHF datasets or monitor user satisfaction with AI outputs. Submit user feedback (Like/Dislike) for a specific AI response log
Example Prompts for Portkey in Cline
Ready-to-use prompts you can give your Cline agent to start working with Portkey immediately.
"Show me the most expensive LLM calls from the last 24 hours"
"Create a budget policy limiting the Marketing team to $500/month on LLM usage"
"Export all logs from last week for our compliance audit"
Troubleshooting Portkey MCP Server with Cline
Common issues when connecting Portkey to Cline through the Vinkius, and how to resolve them.
Server shows error in sidebar
Portkey + Cline FAQ
Common questions about integrating Portkey MCP Server with Cline.
How does Cline connect to MCP servers?
Can Cline run MCP tools without approval?
Does Cline support multiple MCP servers at once?
Connect Portkey with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Portkey to Cline
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.