Any Devin session or MCP-compatible client can create sessions, manage playbooks and knowledge, set up schedules, and more. See Advanced Capabilities for details on what Devin can do.
What is MCP?
The Model Context Protocol (MCP) is an open standard that enables AI apps to securely connect to MCP-compatible data sources and tools. You can think of MCP like a USB-C port for AI applications — a standardized way to connect AI apps to different services.Devin MCP Server
The Devin MCP server is an authenticated service that provides access to both public and private repositories, plus full platform management capabilities. Base Server URL:https://mcp.devin.ai/
Authentication Required
To use the Devin MCP server, you need a Devin API key:- Sign up for a Devin account at Devin.ai
- Generate an API key from your account settings
- Include the API key in your MCP client configuration
Legacy API keys (
apk_ / apk_user_ prefix) are not supported by the Devin MCP server. Use a service user API key instead.Enterprise accounts: X-Org-Id header
Enterprise service user keys and PATs are scoped to the account level, not a specific organization. Since the MCP tools operate on organization-level resources (sessions, playbooks, knowledge, etc.), you must tell the server which organization to target by passing the X-Org-Id header:
Available Tools
Repository Documentation
These tools let you explore and query documentation for any GitHub repository (public or private with authentication):Session Management
Create, search, inspect, and control Devin sessions programmatically:Playbook Management
Create and manage playbooks that standardize how Devin performs tasks:Knowledge Management
Maintain your organization’s knowledge base that Devin uses for context:Schedule Management
Set up recurring or one-time scheduled Devin sessions:Integration Management
View and manage your organization’s native integrations and MCP servers:Wire Protocols
The Devin MCP server supports Streamable HTTP:- URL:
https://mcp.devin.ai/mcp - Works with HTTP-compatible clients
- Recommended for all integrations
The legacy SSE (
/sse) endpoint has been deprecated. Use the /mcp endpoint instead.Key Differences from DeepWiki MCP
Setup Instructions
The field name for the server URL depends on the client: Devin Desktop usesserverUrl, while most other clients use the standard url field. Using the wrong field name causes the MCP server to be silently ignored.
For Devin Desktop:
For most other clients (e.g. Cursor):
For Claude Code:
Related Resources
- Advanced Capabilities — Overview of Devin’s advanced features
- Devin’s MCP Marketplace
- Connecting remote MCP servers to Claude
- OpenAI’s docs for using MCP servers
- DeepWiki MCP — For public repositories only
- DeepWiki
- Ask Devin

