Skip to main content
MCP (Model Context Protocol) lets you connect external tool servers to Devin CLI, giving the agent access to APIs, databases, issue trackers, and any other service you can wrap in an MCP server. When you configure an MCP server, its tools become available to the agent just like built-in tools. The agent can discover what tools are available and call them as needed.

​
How It Works

1

Configure a server

You define an MCP server in your config file with a command, arguments, and optional environment variables.
2

Server launches

Devin CLI starts the server process when needed. The server connects to the external API (GitHub, Linear, etc.).
3

Tool discovery

The agent discovers what tools the server provides (e.g., create_issue, list_repos).
4

Tool execution

When the agent calls an MCP tool, the request flows through the server to the external service and the result is returned.

​
Quick Example

Add a GitHub MCP server to your project: 
// .devin/config.local.json  (gitignored — keep tokens out of committed config)
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token_here"
      }
    }
  }
}
Now the agent can create issues, read PRs, search repos, and more — all through natural language.

​
Permission Control

Once configured, MCP tools appear with a namespaced format: mcp__<server>__<tool>. For example, a “github” server with a “create_issue” tool becomes mcp__github__create_issue. MCP tools are subject to the same permission system as built-in tools. You can control access at multiple levels: 
{
  "permissions": {
    "allow": [
      "mcp__github__*"
    ],
    "deny": [
      "mcp__github__delete_repo"
    ]
  }
}
See Permissions for the full permission syntax.

​
Authentication

Some remote MCP servers (such as Atlassian, Notion, and Linear) require OAuth authentication. Each MCP client authenticates independently — tokens from Windsurf or Claude Code are not shared with Devin CLI. After adding a remote server, authenticate with: 
devin mcp login <server-name>
This opens a browser window for the OAuth flow. See MCP Configuration — Authentication for details.

​
Next Steps

Configuration

Learn how to configure MCP servers in detail

Permissions

Control which MCP tools the agent can use