Govern Claude models, Claude Code, and Claude Desktop¶
WSO2 API Platform works alongside the Anthropic products you already use. Govern traffic to Claude models, route Claude Code through AI Gateway, and give Claude Desktop and Claude Code controlled access to APIs and MCP servers.
End-to-end guides and tutorials¶
Step-by-step guides for Claude Code and Claude Desktop. Guides are part of this documentation. Tutorials are published on the WSO2 API Platform Learn Hub and written for the product version they name.
-
Configure Claude Code with AI Gateway
Route Claude Code requests through an Anthropic provider and an App LLM Proxy.
Guide · Anthropic API key · Hybrid
-
Configure Claude Code with AI Gateway using a Claude subscription
Route Claude Team or Enterprise traffic through AI Gateway with enterprise identity.
Guide · Claude subscription · Hybrid, Self-hosted
-
Build an AI app with Claude Code that calls governed APIs
Give Claude Code governed, rate-limited access to your backend APIs.
Guide · Claude Code · Cloud
-
Convert a REST API into an MCP tool for Claude Desktop
Expose a REST API as a governed MCP server and use it in Claude Desktop.
Guide · Claude Desktop · Cloud
-
Find and connect to an enterprise MCP server from the MCP Hub
Find an approved MCP server, generate client configuration, and connect Claude Desktop or Claude Code to it.
Guide · Claude Desktop and Claude Code · Cloud
-
Control Claude Code costs across a large engineering team
Add token limits, cost caps, semantic caching, prompt compression, and per-developer spend visibility to a shared Claude Code setup.
Learn Hub tutorial · Anthropic API key · Hybrid, Self-hosted
Choose a billing model
With an Anthropic API key, the gateway holds the key and Anthropic charges per token. Developers never see the Anthropic key. With a Claude Team or Enterprise subscription, the gateway forwards each developer's Claude token to Anthropic and authenticates the developer against your identity provider.
AI Gateway with Claude models¶
Route, secure, and govern traffic to Claude models through WSO2 AI Gateway, including traffic from Claude Code.
Anthropic as an LLM provider¶
Connect the Anthropic API. The gateway holds the Anthropic key, so developers and applications never see it.
Token limits, semantic caching, and the other AI API policies work the same way for every provider. See AI APIs.
Routing, token limits, cost control, and the other AI Workspace policies work the same way for every provider. See the AI Workspace overview.
Routing, token limits, cost control, and the gateway's other policies work the same way for every provider. See the AI Gateway documentation.
Claude Desktop and MCP tools¶
Expose your APIs and MCP servers to Claude Desktop and Claude Code through governed MCP proxies. Tool calls go through the gateway. Requests to Claude models go directly to Anthropic unless you also route them through AI Gateway.
Architecture and responsibility model¶
WSO2 API Platform and Anthropic split the work like this:
| Scenario | WSO2 role | Anthropic role | Runtime traffic |
|---|---|---|---|
| Claude Code through AI Gateway | Authenticates developers and applies guardrails, rate limits, and analytics | Hosts the Claude models and bills the API key or subscription | Goes through WSO2 AI Gateway to Anthropic |
| Applications calling Claude models | Proxies and governs LLM requests | Hosts the Claude models | Goes through WSO2 AI Gateway to Anthropic |
| Claude Desktop and Claude Code with governed tools | Proxies and governs your APIs and MCP servers | Provides the Claude client and model | Tool calls go through WSO2, and model requests go directly to Anthropic |
Learn more¶
Related pages in the Anthropic documentation:
- Claude Code LLM gateway configuration
- Claude models overview
- Claude API overview
- Connect to remote MCP servers
To browse every guide by goal, see the Guides overview.