How to integrate Devin MCP with Google ADK

Connect Google ADK 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

This guide walks you through connecting Devin to Google ADK using the Composio tool router. By the end, you'll have a working Devin agent that can summarize codebase structure for devin-ai/devin, list all open pull requests for a repo, generate documentation summary for private repository through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Devin account through Composio's Devin MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Devin MCP with

TL;DR

Here's what you'll learn:
  • Get a Devin account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Devin
  • Build an agent that connects to Devin through MCP
  • Interact with Devin using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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 step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Devin via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["devin_mcp"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Devin operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Devin MCP and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["devin_mcp"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Devin operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Devin with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Devin using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Devin tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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. Google ADK 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