Hosted MCP: Connect Claude to Xplorr in 2 Minutes
import { Steps } from ‘@astrojs/starlight/components’;
Hosted MCP (No Setup Required)
Section titled “Hosted MCP (No Setup Required)”Xplorr runs a hosted MCP endpoint at https://mcp.xplorr.io/mcp. This is the fastest way to connect Claude to your cost data — no servers to manage, no Docker containers, no Node.js installation.
-
Get your API token
Log in to console.xplorr.io, go to Settings > API Tokens, and click Create Token. Copy it.
-
Add Xplorr to your Claude client
Pick the client you use:
Claude Desktop (macOS): Edit
~/Library/Application Support/Claude/claude_desktop_config.json:{"mcpServers": {"xplorr": {"url": "https://mcp.xplorr.io/mcp","headers": {"Authorization": "Bearer xplorr_your_token_here"}}}}Claude Desktop (Windows): Edit
%APPDATA%\Claude\claude_desktop_config.jsonwith the same content.Claude Code: Add the MCP server from the command line:
Terminal window claude mcp add xplorr \--transport http \--url https://mcp.xplorr.io/mcp \--header "Authorization: Bearer xplorr_your_token_here"Claude.ai (web): MCP connections are configured in Settings > Integrations if your plan supports it. Add the URL
https://mcp.xplorr.io/mcpwith the Authorization header.Replace
xplorr_your_token_herewith your actual token in all cases. -
Restart your Claude client
Close and reopen Claude Desktop, or restart Claude Code. The Xplorr tools appear in Claude’s tool list (26 tools).
Verify It Works
Section titled “Verify It Works”Ask Claude:
“List my connected cloud accounts”
Claude should return a list of your connected AWS, Azure, and/or GCP accounts. If you see them, everything is working.
Try a few more:
“What are my top 5 most expensive services this month?”
“Show me cost anomalies in the last 7 days”
“Forecast my end-of-month spend”
Troubleshooting
Section titled “Troubleshooting”“No tools available” or Xplorr not showing in tool list
- Make sure you saved the config file and restarted Claude
- Verify the JSON is valid (no trailing commas, correct quotes)
- Check that the URL is exactly
https://mcp.xplorr.io/mcp(with/mcpat the end)
“Unauthorized” or “Invalid token” errors
- Verify your token starts with
xplorr_ - Make sure there are no extra spaces around the token
- Try creating a new token in Settings > API Tokens
Tools show up but return “No data”
- Make sure you have at least one cloud account connected in Xplorr
- Check if the account has synced successfully (Settings > Cloud Accounts)
When to Self-Host Instead
Section titled “When to Self-Host Instead”Consider self-hosting the MCP server if:
- Your compliance rules prevent outbound API calls to third-party endpoints
- You’re running the Xplorr backend on-premises with a custom URL
- You need to run the MCP server inside a private network or VPN
- You want to pin a specific MCP server version for stability
For most users, the hosted endpoint is the simplest and recommended option.
Is the hosted endpoint always available? The hosted endpoint runs on the same infrastructure as the Xplorr platform. Uptime matches the main service.
Is my data encrypted in transit? Yes. All connections use HTTPS/TLS. Your API token and cost data are encrypted between Claude and the Xplorr endpoint.
Can I use the hosted endpoint with non-Claude MCP clients?
Yes. Any MCP-compatible client that supports HTTP transport can connect to https://mcp.xplorr.io/mcp.
Does the hosted endpoint cost extra? No. It’s included in all Xplorr plans.
Related Guides
Section titled “Related Guides”- MCP Overview — All 26 tools and how the server works
- MCP Tools Reference — Detailed tool parameters and responses
- Self-Host with Docker — Run the MCP server in a container
- Self-Host with Node.js — Run the MCP server locally
- API Authentication — Token creation and management