> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asisso.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Connect Claude and other AI assistants to your Asisso workspace via the Model Context Protocol

## Overview

Asisso exposes an [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that lets AI assistants like Claude Code, Claude Desktop, and Cursor access your workspace and documentation. Once connected, an assistant can list your agents, fetch agent definitions, and search Asisso docs on your behalf.

## Prerequisites

* An Asisso API key. Generate one at [`app.asisso.com/api-keys`](https://asisso.com/app/api-keys). See [API Keys](/configurations/api-keys).
* Your Asisso MCP endpoint: `https://app.asisso.com/api/v1/mcp/`

The endpoint is also shown in **Platform Settings → MCP Server** inside the Asisso dashboard.

## Claude Code

Register Asisso as an MCP server with the Claude Code CLI:

```bash theme={null}
claude mcp add --transport http asisso https://app.asisso.com/api/v1/mcp/ \
  --header "X-API-Key: YOUR_API_KEY"
```

Replace `YOUR_API_KEY` with the key you generated.

Verify the server is connected:

```bash theme={null}
claude mcp list
```

## Claude Desktop

Open Claude Desktop's config file (`claude_desktop_config.json`) and add the `asisso` entry under `mcpServers`:

```json theme={null}
{
  "mcpServers": {
    "asisso": {
      "url": "https://app.asisso.com/api/v1/mcp/",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}
```

Restart Claude Desktop after saving. The Asisso tools should appear in the tool picker.

## Cursor and other MCP clients

Any MCP client that supports Streamable HTTP transport can connect with the same URL and header. Paste the configuration above into your client's MCP settings file and replace `YOUR_API_KEY`.

## Example prompts

Once the MCP server is connected, you can drive Asisso from your coding agent in plain English. A few prompts to try:

**Explore your workspace**

* "List my agents in Asisso."
* "Show me the definition of the agent called *Lead Qualifier*."
* "Which credentials and tools are configured in my Asisso workspace?"
* "List the recordings from my most recent agent."

**Edit an agent**

* "In my *Lead Qualifier* agent, add a new agent node after the greeting that asks the caller for their budget, then routes to the existing qualification node."
* "Add an end-call node to *Support Bot* that triggers when the user says they are done, with a polite goodbye prompt."
* "Rename the *intro* node in *Lead Qualifier* to *greeting* and update any edges that reference it."
* "Change the LLM model on all agent nodes in *Support Bot* to `gpt-4o-mini`."

**Learn the platform**

* "Search the Asisso docs for how to configure a TURN server."
* "What node types does Asisso support, and what fields does a `knowledge_base` node take?"
* "How do I trigger an outbound call from the Asisso API?"

<Note>
  Agent edits are saved as a new **draft** version — your published agent keeps serving calls until you explicitly publish the draft from the Asisso UI.
</Note>

<Note>
  The API key controls which workspace the assistant sees. Treat it like any other credential — do not commit it to source control or paste it into shared chats.
</Note>