Skip to main content
The Tuner MCP server lets your AI assistant read and change your Tuner workspace. You can configure an agent’s outcomes, intents, evals, red flags and alerts by describing what you want, and ask questions about your calls.
The Tuner MCP server is in Beta. Available actions and supported clients may change.

Why use it

Describe several outcomes, evals and intents in one message, and the assistant creates them together. Your assistant can also see your codebase, your agent’s system prompt and your call flows. Ask “based on my agent’s system prompt, suggest the right call outcomes and evals” to get a configuration that matches how your agent works.

Supported clients

Tuner MCP server URL: https://api.usetuner.ai/mcp/

Open the setup instructions in Tuner

Tuner shows the same instructions with your IDs filled in:
  • While creating an agent, pick Configure via MCP in the setup wizard. See the Quickstart.
  • For an existing agent, click Configure with MCP at the top of Agent Settings. The dialog has Step 1: Connect to your AI client and Step 2: Start the setup, with a prompt you can copy.
The Configure with MCP dialog: IDE and chat app tabs, the Cursor, Claude Code and Antigravity options, setup steps and the server configuration to paste

IDEs

IDEs authenticate with a Tuner API key sent as a bearer token. Create one on the API Keys page; see API keys and IDs. A key is shown only when you create it.

Cursor

1

Open MCP settings

Go to Settings > Tools & MCP and click Add Custom MCP to open your mcp.json.
2

Paste the configuration

Add the following to your mcp.json:
Replace YOUR_TUNER_API_KEY with your Tuner API key.

Claude Code

1

Run the add command

Open your terminal inside Claude Code and run:
Replace YOUR_TUNER_API_KEY with your Tuner API key.

Antigravity

1

Open the MCP configuration

Click the … dropdown at the top of the editor’s agent panel, then Manage MCP Servers > View raw config to open mcp_config.json.
2

Paste the configuration

Add the following to your mcp_config.json:
Replace YOUR_TUNER_API_KEY with your Tuner API key.

Chatbots

Chatbots authenticate with OAuth. The first time you add the server, you’re redirected to Tuner to sign in and authorize access.

Claude

1

Add a custom connector

Go to Customize > Connectors, click the plus icon, click Add Custom Connector, and paste the Tuner MCP server URL:
2

Connect and authenticate

Click Connect. You will be redirected to Tuner to sign in and authorize access.
3

Enable Tuner in your chat

When starting a new chat, click the + button and verify Tuner is toggled on under Connectors.

Start the setup

Once connected, paste this into your chat. Configure with MCP in Tuner gives you this prompt with your values filled in.
To find your workspace ID, open Workspace Settings > General Settings. Your agent’s details are on Agent Settings > Agent Setup. See API keys and IDs. You can also ask the assistant to list the agents in your workspace.
The tuner_setup_agent prompt walks your assistant through defining your call outcomes, intents, data-extraction fields, evals, red flags and alerts in one conversation.

What the MCP server can do

The server gives your assistant these tools, for the workspaces your account or key can access. It also has prompts that guide the assistant through a task. Ask the assistant to fetch one by name: Simulations, datasets, API keys and workspace settings are managed in the dashboard.

Example prompts

Bulk setup from a description:
“I have a restaurant booking agent. Create the following call outcomes: Reservation Booked (Success), Reservation Modified (Success), Customer Cancelled (Failure), No Availability (Failure), and General Inquiry (Success). Also add user intents for: Make a Reservation, Modify a Reservation, Cancel a Reservation, and Ask About Menu.”
Several evals at once:
“Add these evals: Did the agent confirm the reservation date and time? Did the agent ask for the party size? Did the agent offer alternative times when the requested slot was unavailable?”
Reading your current setup:
“List all agents in my workspace and show me a summary of how each one is configured.”

Best practices

Detail gets better results. Instead of “add some call outcomes”, try “for my Customer Support agent, add a call outcome called ‘Appointment Booked’ with type Success, defined as: the customer scheduled an appointment with a confirmed date and time.” If you have multiple agents, always say which one.
Describe all your outcomes, intents, and evals in one message. The assistant creates them together.
Ask your assistant to list the current settings afterwards, so you can verify everything looks right before calls start flowing.
Use the MCP server for configuration and diagnosis. Track live results and trends over time in the Tuner dashboard.

Troubleshooting

  • Chatbots: Check that you’re using the correct MCP server URL and that your Tuner account is active.
  • IDEs: Check that your API key is valid and correctly placed in the configuration file. Make sure https://api.usetuner.ai/mcp/ is reachable.
  • Chatbots: Disconnect and reconnect. In Claude, go to Customize > Connectors, remove Tuner, then add it again.
  • IDEs: Check that the key hasn’t been revoked on the API Keys page. If you no longer have it, create a new key and update your configuration file.
  • Claude: Click the + button and check that Tuner is toggled on under Connectors.
  • IDEs: Verify the MCP server configuration is saved correctly and restart the IDE if needed.

Next steps

Diagnose your agent

Once calls are flowing, use the MCP server to find what’s broken, understand why, and fix it.

Call outcomes and intents

What you’re configuring when you set these up through MCP.