How to integrate Devin MCP with Claude Code

Connect Claude Code to Devin MCP. Summarize codebase structure for devin-ai/devin, list all open pull requests for a repo, and more using natural language, with authentication handled for you.

Devin MCP logoDevin MCP
Api Key

Devin MCP is an AI-powered integration for accessing and analyzing GitHub repositories and documentation. It enables secure, automated codebase intelligence, even for private repos.

23 Tools

Introduction

Manage your Devin directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Devin MCP with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1500+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Devin to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Devin MCP server, and what's possible with it?

The Devin MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Devin account. It provides structured and secure access to your repository documentation and Devin workflows, so your agent can explore codebases, generate wikis, coordinate sessions, review code, and manage automations on your behalf.

  • Repository research and documentation: Have your agent list indexed repositories, generate codebase wikis, browse documentation topics and content, or ask questions grounded in a repository.
  • Devin session coordination: Direct your agent to create and search sessions, interact with active work, inspect session events, and wait for multiple sessions to finish.
  • Code reviews and security scans: Instruct your agent to trigger reviews, check review status and findings, and manage code security scans.
  • Automations and team knowledge: Let the agent manage Devin automations, playbooks, schedules, knowledge notes, suggestions, and on-call workflows.
  • Integrations and organization settings: Have your agent list users and integrations, manage MCP server installations and billing tags, or find specific Devin settings.

Connecting Devin MCP via Composio SDK

Composio SDK is the underlying technology that powers these integrations. It provides a universal gateway with full programmatic control. You can programmatically generate an MCP URL with the app you need (here Devin MCP) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Devin account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['devin_mcp'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http devin_mcp-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Devin. This URL will be used to connect Claude Code to Devin.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Devin
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Devin MCP to Claude Code

bash
claude mcp add --transport http devin_mcp-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (devin_mcp-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Devin MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your devin_mcp-composio entry in the list
  • This confirms that Claude Code can now access Devin tools

If everything is wired up, you should see your devin_mcp-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Devin

The first time you try to use Devin tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Devin
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Devin authorization flow
  • Return to the terminal and start using Devin through Claude Code

Once authenticated, you can ask Claude Code to perform Devin operations in natural language. For example:

  • "Summarize codebase structure for devin-ai/devin"
  • "List all open pull requests for a repo"
  • "Generate documentation summary for private repository"

Complete Code

Here's the complete code to get you started with Devin MCP and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['devin_mcp'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http devin_mcp-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Devin with Claude Code using Composio's MCP server. Now you can interact with Devin directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Devin operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Devin operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every Devin MCP action and event your agent gets out of the box.

Ask wiki question

Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.

Devin automation manage

Manage Devin automations.

Devin billing tag manage

Manage Devin billing tags (groupings of Devin sessions for usage tracking) with a single action-based tool: list/get/create tags, assign sessions one at a time or in bulk (up to 500 per call, sent in sequential batches of 100), and read the billing tags of up to 100 sessions at once ('get_session_tags').

Devin blueprint test

Test a candidate blueprint YAML in an authoring VM: start → run initialize → fix → run initialize again (clean VM) → run maintenance → then persist with update_environment_config.

Devin code scan manage

Manage Devin code scans (sometimes referred to as "security scans" or "Devin Security Swarm").

Devin find setting

Find a Devin webapp setting and get a deep-link URL to it.

Devin knowledge manage

Manage Devin knowledge notes and suggestions via a single action-based tool.

Devin list integrations

List native integrations and MCP servers for the organization, with status and settings/install URLs.

Devin mcp server manage

Manage MCP server installations for the organization: install (from the marketplace or custom), update, delete, enable, or disable.

Devin oncall manage

Manage Devin Oncall.

Devin playbook manage

Manage Devin playbooks with a single action-based tool.

Devin review manage

Trigger a Devin Review for a pull/merge request, fetch the latest review status for one, or fetch a completed review's findings.

Devin schedule manage

Manage scheduled Devin sessions (deprecated in favor of Automations).

Devin session create

Create one or more child Devin sessions via the v3 REST API.

Devin session events

Inspect events within a Devin session — list summaries, fetch full details, or search.

Devin session gather

Wait for multiple Devin sessions to reach a settled state before returning.

Devin session interact

Consolidated tool for all interactions with a single Devin session.

Devin session search

Search and filter Devin sessions.

Devin user list

List the current organization's users, one membership kind per call.

Generate wiki

Generate a codebase wiki for a repository.

List wiki repos

List the repositories that have a DeepWiki index, i.

Read wiki contents

View documentation about a GitHub repository.

Read wiki structure

Get a list of documentation topics for a GitHub repository.

FAQ

Frequently asked questions

With a standalone Devin MCP server, the agents and LLMs can only access a fixed set of Devin tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Devin and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Devin tools.

Yes, absolutely. You can configure which Devin scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Devin data and credentials are handled as safely as possible.

Start with Devin MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Devin MCP tool your agent needs.Free to start.

Start building