Documentation Index
Fetch the complete documentation index at: https://docs.sf-voice.sh/llms.txt
Use this file to discover all available pages before exploring further.
The Mise MCP server is an npm package that runs locally and connects your AI assistant to your Mise call corpus. Once configured, your assistant can query calls, fetch replay bundles, and inspect defect signatures without leaving the chat.
Prerequisites
Before you start, you need:
- A Mise account in private alpha. Request access if you do not have one yet.
- An AI assistant that supports MCP: Claude Desktop, Cursor, or Cline.
- Node.js 18 or later installed on your machine (
node --version to check).
- Your Mise API key (see Finding your API key below).
MCP server credentials are issued after alpha access is granted. If your account is active but you do not see an API key in Settings, contact your Mise onboarding contact.
Finding your API key
Your API key is in the Mise dashboard under Settings → API Keys. Click New key, name it (e.g. mcp-local), and copy the value. You will not be able to view it again after leaving the page.
Setup instructions
Claude Desktop
Cursor
Cline
Claude Desktop is the primary supported client for the Mise MCP server.Open your Claude Desktop config file
The config file is at:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
If the file does not exist, create it. Add the Mise server
Add a mcpServers entry for Mise. If you already have other servers configured, add "mise" alongside them.claude_desktop_config.json
{
"mcpServers": {
"mise": {
"command": "npx",
"args": ["-y", "@mise/mcp-server"],
"env": {
"MISE_API_KEY": "your-api-key-here"
}
}
}
}
your-api-key-here with your actual API key. Restart Claude Desktop
Quit and relaunch Claude Desktop. The Mise tools will appear in the tool list when you start a new conversation.
Verify the connection
Start a new conversation and send this prompt:List the available Mise tools.
Open Cursor MCP settings
In Cursor, open the command palette (Cmd+Shift+P / Ctrl+Shift+P) and search for MCP: Open Settings, or go to Settings → MCP Servers.
Add the Mise server config
Add the following entry to your Cursor MCP configuration file (~/.cursor/mcp.json):{
"mcpServers": {
"mise": {
"command": "npx",
"args": ["-y", "@mise/mcp-server"],
"env": {
"MISE_API_KEY": "your-api-key-here"
}
}
}
}
your-api-key-here with your actual API key. Reload the MCP server
Save the file and use MCP: Reload Servers from the command palette to pick up the new configuration.
Verify the connection
Open Cursor Chat and send:List the available Mise tools.
Open Cline MCP settings
In VS Code with Cline installed, click the Cline icon in the sidebar and go to MCP Servers → Configure MCP Servers.This opens the Cline MCP settings file (cline_mcp_settings.json).
Add the Mise server config
Add a mise entry to the mcpServers object:{
"mcpServers": {
"mise": {
"command": "npx",
"args": ["-y", "@mise/mcp-server"],
"env": {
"MISE_API_KEY": "your-api-key-here"
}
}
}
}
your-api-key-here with your actual API key. Reload the server
Save the file. Cline will detect the new server and connect automatically. You can verify the status in the MCP Servers panel — the Mise server should show as Connected.
Verify the connection
Open a new Cline chat and send:List the available Mise tools.
Environment variable reference
Store your API key in the env block of your MCP config file, not in shell profiles or .env files. The MCP server reads environment variables from the config only.
| Variable | Required | Description |
|---|
MISE_API_KEY | Yes | Your Mise API key from Settings → API Keys. |
MISE_PROJECT_ID | No | Scopes all queries to a single project. Useful if your account has multiple voice stacks. |
Next steps
Once the server is connected, see AI-assisted debugging for a complete walkthrough of the replay → root cause workflow.