2,500+ MCP servers ready to use
Vinkius

Portkey MCP Server for AutoGen 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Portkey as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="portkey_agent",
            tools=tools,
            system_message=(
                "You help users with Portkey. "
                "10 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
Portkey
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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:

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Portkey tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

  • 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 AutoGen 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 AutoGen via MCP

Follow these steps to integrate the Portkey MCP Server with AutoGen.

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 10 tools from Portkey automatically

Why Use AutoGen with the Portkey MCP Server

AutoGen provides unique advantages when paired with Portkey through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Portkey tools to solve complex tasks

02

Role-based architecture lets you assign Portkey tool access to specific agents. a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive Portkey tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes Portkey tool responses in an isolated environment

Portkey + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Portkey MCP Server delivers measurable value.

01

Collaborative analysis: one agent queries Portkey while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from Portkey, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using Portkey data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process Portkey responses in a sandboxed execution environment

Portkey MCP Tools for AutoGen (10)

These 10 tools become available when you connect Portkey to AutoGen via MCP:

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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

10

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 AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Portkey immediately.

01

"Show me the most expensive LLM calls from the last 24 hours"

02

"Create a budget policy limiting the Marketing team to $500/month on LLM usage"

03

"Export all logs from last week for our compliance audit"

Troubleshooting Portkey MCP Server with AutoGen

Common issues when connecting Portkey to AutoGen through the Vinkius, and how to resolve them.

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Portkey + AutoGen FAQ

Common questions about integrating Portkey MCP Server with AutoGen.

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Portkey tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect Portkey to AutoGen

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.