AI-powered access to GitHub repository documentation and codebase analysis, including private repositories, via Devin.
AI-powered access to GitHub repository documentation and codebase analysis, including private repositories, via Devin. On Nagent, Devin MCP is exposed as a fully-configurable model context protocol integration that any agent can call — 4 actions, and API key authentication. No code is required to wire Devin MCP into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Devin MCP to automate the kinds of tasks model context protocol teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Devin MCP into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Devin MCP, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DEVIN_MCP_ASK_QUESTIONAsk any question about a GitHub repository and get an AI-powered, context-grounded response. Args: repoName: GitHub repository or list of repositories (max 10) in owner/repo format question: The question to ask about the repository
Input parameters
Output
DEVIN_MCP_LIST_AVAILABLE_REPOSList all repositories available to query with your Devin account. Only available in private mode (via devin.ai endpoints).
Output
DEVIN_MCP_READ_WIKI_CONTENTSView documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
Input parameters
Output
DEVIN_MCP_READ_WIKI_STRUCTUREGet a list of documentation topics for a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")
Input parameters
Output
No publicly available marketplace agent is found using this tool yet. There are 39 agents privately built on Nagent that already use Devin MCP.
Build on Nagent
Connect Devin MCP to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Devin MCP, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Devin MCP is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Devin MCP is connected, you configure its 4 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Devin MCP steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Devin MCP event fires, the agent kicks off automatically.
Every Devin MCP action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Devin MCP ships with 4 pre-built model context protocol actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Devin MCP together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Devin MCP-based workflows tailored to your business.