Can I check the budget and rate limits for a specific proxy key?

Yes. Use the `get_key_info` tool with the specific Key ID. Your agent will retrieve the exact rate limits, budget constraints, and current RPM usage associated with that token.

How do I see the model fallback paths configured in my proxy?

The `get_model_info` tool allows your agent to extract the global model directory. You'll see the exact fallback chains (e.g., if OpenAI fails, use Anthropic) and the physical endpoints assigned to each model name.

Can my agent create a new team to track specific division costs?

Absolutely. Use the `create_team` tool and provide a JSON payload defining the team name and optional budget limits. Your agent will provision the new team identity in LiteLLM, allowing for precise organizational cost tracking.

LiteLLM (LLM Proxy & Spend Tracking) MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: LiteLLM (LLM Proxy & Spend Tracking)
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install LiteLLM (LLM Proxy & Spend Tracking) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "litellm-llm-proxy-spend-tracking": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 LiteLLM (LLM Proxy & Spend Tracking) MCP Server

Connect your LiteLLM Proxy instance to any AI agent and take full control of your LLM infrastructure, load balancing, and spend management through natural conversation.

GitHub Copilot Agent mode brings LiteLLM (LLM Proxy & Spend Tracking) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Key Orchestration — Generate and manage proxy API keys to isolate distinct microservices or teams, including precise budget and rate limit constraints directly from your agent
Model Routing Intelligence — Get detailed info on fallback paths (e.g., OpenAI -> Anthropic -> Groq) and verify exact routing endpoints assigned to your models
Real-time Spend Audit — Track total USD consumed by specific end-users or teams and monitor budget ceilings to ensure cost-effective AI deployments
Dynamic Model Control — Inject fresh routing endpoints (e.g., new AWS Bedrock or Azure OpenAI deployments) into your proxy runtime with zero downtime
Team & Organizational Isolation — Create and manage team profiles to track exact cost limits and operational boundaries per organizational division
Infrastructure Security — Instantly vaporize malicious or leaked keys and remove broken LLM deployments to prevent downstream 500 errors dynamically

The LiteLLM (LLM Proxy & Spend Tracking) MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot 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 LiteLLM (LLM Proxy & Spend Tracking) to VS Code Copilot via MCP

Follow these steps to integrate the LiteLLM (LLM Proxy & Spend Tracking) MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using LiteLLM (LLM Proxy & Spend Tracking)

Ask Copilot: "Using LiteLLM (LLM Proxy & Spend Tracking), help me...". 10 tools available

Why Use VS Code Copilot with the LiteLLM (LLM Proxy & Spend Tracking) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with LiteLLM (LLM Proxy & Spend Tracking) through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

LiteLLM (LLM Proxy & Spend Tracking) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the LiteLLM (LLM Proxy & Spend Tracking) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

LiteLLM (LLM Proxy & Spend Tracking) MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect LiteLLM (LLM Proxy & Spend Tracking) to VS Code Copilot via MCP:

create_model

Inject completely fresh routing endpoints (ex: new Bedrock Llama 4 endpoints)

create_team

Generate pristine organizational isolation tracking exact cost limits per division

create_user

Insert specific End-User identities bridging Vinkius with Proxy logs

delete_key

Delete an existing LLM proxy key entirely

delete_model

Delete explicitly routed LLM deployments preventing 500s dynamically

generate_key

Generate a new proxy API key isolating distinct microservices or teams

get_key_info

Get configuration and budget bounds for a specific LiteLLM API Key

get_model_info

Get array endpoints tracing exact Fallback paths like OpenAI -> Anthropic

get_team_info

Get internal logic bounds matching multiple routing users via Team UUID

get_user_info

Return precise End-User abstractions tracking total USD consumed natively

Example Prompts for LiteLLM (LLM Proxy & Spend Tracking) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with LiteLLM (LLM Proxy & Spend Tracking) immediately.

"List all active model fallback paths in LiteLLM"

"Generate a new API key for the 'Customer-Service' team with a $50 monthly budget"

"How much has user 'alex_dev' spent on LLM tokens today?"

Troubleshooting LiteLLM (LLM Proxy & Spend Tracking) MCP Server with VS Code Copilot

Common issues when connecting LiteLLM (LLM Proxy & Spend Tracking) to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

LiteLLM (LLM Proxy & Spend Tracking) + VS Code Copilot FAQ

Common questions about integrating LiteLLM (LLM Proxy & Spend Tracking) MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.