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

# Devin

> Connect Devin to Autosana through MCP

Connect Devin so you can list flows, run them, debug runs, and search Autosana docs from a Devin session.

Autosana is a remote HTTP MCP server. In Devin's **Add a custom MCP** form, switch **Transport type** to **HTTP**. Leave **STDIO** — that form is for a local command you run yourself.

Adding a custom MCP in Devin requires permission to manage MCP servers. If you do not see **Add a custom MCP**, ask an organization admin or use **Suggest MCP Integration**.

## Setup

1. Go to **[Settings → Integrations → Devin](https://autosana.ai/settings?tab=integrations\&integration=devin)** and click **Create key and copy**
2. In Devin, open **Customize → MCPs → Add a custom MCP**
3. Set **Transport type** to **HTTP** (not STDIO)
4. Fill in:

```
Server name: Autosana
Transport: HTTP
Server URL: https://mcp.autosana.ai/mcp
Authentication: Auth Header
Header key: x-api-key
Header value: <YOUR_API_KEY>
```

5. Save, then click **Test listing tools** to confirm Devin can see Autosana's tools
6. Start a new session and ask Devin to list or run a flow

<Note>
  The custom MCP form defaults to STDIO (command, arguments, environment variables). Autosana is not a local process. Do not paste `npx`, `mcp-remote`, or a shell command there.
</Note>

<Note>
  Use **Auth Header** with the header name `x-api-key`. Do not use `Authorization: Bearer`. Adding Autosana in Cursor (`mcp.json`) does not install it in Devin.
</Note>

See [MCP Server](/mcp-setup) for the tools Devin can call after you connect.