Overview

FinOps provides 100% compatible endpoints for OpenAI, Anthropic, and Gemini APIs, making it seamless to integrate with any agent that uses these providers. Point each agent at the FinOps URL shape it expects (see Configuration below and the guide for your tool). That unlocks:

Universal Model Access: Use any provider/model configured in FinOps with any agent (e.g., use GPT-5 with Claude Code, or Claude Sonnet 4.5 with Codex CLI)
MCP Tools Integration: All Model Context Protocol tools configured in FinOps become available to your agents
Built-in Observability: Monitor all agent interactions in real-time through FinOps's logging dashboard
Load Balancing: Automatically distribute requests across multiple providers and regions
Advanced Features: Governance, caching, failover, and more - all transparent to your agent

If your Allowed Headers are already set to *, you can skip this note. If not and you face issues integrating FinOps with your CLI agent, try switching to * or adding the specific headers required by your client. By default, FinOps whitelists: Content-Type, Authorization, X-Requested-With, X-Stainless-Timeout, and X-Api-Key.

CLI Agents

LibreChat — Open-source chat client supporting multiple providers
Open WebUI — ChatGPT-like open-source chat interface
Claude Code — AI-powered coding directly in your terminal
Claude for Office — Claude in Word, Excel, PowerPoint, and Outlook
Claude Desktop — Route Claude Desktop App's Code tab through any provider
Codex CLI — OpenAI's powerful code generation CLI
Gemini CLI — Google's coding assistant with advanced reasoning
Qwen Code — Alibaba's coding assistant
Opencode — Terminal-based coding assistant by SST

Editors

Cursor — AI-powered IDE with MCP integration and virtual key support
Zed Editor — High-performance editor with AI integration
Roo Code — AI-powered VS Code extension with multi-provider support

Configuration

OpenAI-compatible URL shape varies by client: tools such as Codex CLI need the API base to end with /v1 (e.g. https://your-gateway/openai/v1). Official OpenAI SDKs often take https://your-gateway/openai and add /v1 to request paths. Use the page for your agent to avoid 404s or wrong-host errors.

Agent integrations work with your existing FinOps configuration. Ensure you have:

Providers configured: See Provider Configuration for setup details
Optional: MCP tools: See MCP Integration to enhance agent capabilities

Monitoring Agent Traffic

All agent interactions are automatically logged and can be monitored at {AI_GATEWAY_URL}/logs. You can filter by provider, model, or search through conversation content to track your agents' performance.

For complete monitoring capabilities, see Built-in Observability.

MCP Tools Integration

This feature is only available on v1.4.0-prerelease1 and above.

FinOps exposes all configured MCP tools through a dedicated MCP server endpoint at /mcp. This allows external MCP clients (Claude Code, Cursor, and other MCP-compatible applications) to connect directly and access your tools.

Connect Claude Code to FinOps MCP

Add FinOps as an MCP server to Claude Code:

claude mcp add --transport http finops {AI_GATEWAY_URL}/mcp

Using Virtual Key Authentication:

If you have virtual key authentication enabled in FinOps, connect using the JSON configuration format:

claude mcp add-json finops '{"type":"http","url":"{AI_GATEWAY_URL}/mcp","headers":{"Authorization":"Bearer bf-virtual-key"}}'

Replace bf-virtual-key with your actual FinOps virtual key.

Claude Code will only have access to the specific MCP tools permitted by the virtual key's configuration. To grant access to additional tools, verify or modify the virtual key's MCP tool permissions in the FinOps dashboard.

Supported Agents

You can connect any MCP-compatible client to FinOps's MCP server:

Claude Code - Add via claude mcp add command
Cursor IDE - Configure in cursor settings
Custom Applications - Any app implementing the MCP protocol

Tool Access Control

Control which tools each client can access using Virtual Keys:

Create a Virtual Key for each client/environment
Configure which MCP servers and tools the key can access
FinOps automatically enforces these permissions

For complete setup instructions and tool filtering options, see MCP Gateway URL.

Next Steps

Provider Configuration - Configure AI providers for your agents
Governance - Set usage limits and policies for your agents
Integrations - Understand how FinOps works with existing AI provider SDKs

Overview

On this page