Devin

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

Go to Settings → Integrations → Devin and click Create key and copy
In Devin, open Customize → MCPs → Add a custom MCP
Set Transport type to HTTP (not STDIO)
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>

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

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.

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.

See MCP Server for the tools Devin can call after you connect.

Getting Started

Core Features

Best Practices

Code-Managed Flows

Guides

Integrations

Uploading Your App

APIs

Setup

​Setup

Setup