devin-api-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVIN_ORG_ID | No | Optional organization ID (auto-discovered for v3). | |
| DEVIN_API_KEY | No | Fallback API key for v1 (backward compatibility). | |
| DEEPWIKI_UPSTREAM_URL | No | Upstream URL for deepwiki proxy (default https://mcp.devin.ai/mcp). | |
| DEVIN_SERVICE_API_KEY | No | Service API key (prefix cog_) for v3 server. | |
| DEVIN_PERSONAL_API_KEY | No | Personal API key (prefix apk_user_) for v1 and deepwiki servers. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_questionA | Ask any question about a GitHub repository and get an AI-powered, context-grounded response. |
| read_wiki_contentsC | View documentation about a GitHub repository. |
| read_wiki_structureA | Get a list of documentation topics for a GitHub repository. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: ask_question provides AI-powered answers, read_wiki_contents retrieves full documentation, and read_wiki_structure lists available topics. There is no meaningful overlap between asking questions and reading wiki docs.
All tools follow a consistent verb_noun pattern: ask_question, read_wiki_contents, read_wiki_structure. Naming is uniform and predictable.
With only three tools, the server is tightly scoped to AI-powered repository Q&A and wiki access. This is well within the ideal range and each tool is essential to the core purpose.
The set covers the primary workflows: asking questions and reading wiki documentation. A minor gap is the lack of functionality beyond wiki content (e.g., general repository file browsing), but for the stated AI Q&A focus it is sufficient.