MCP-Devin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVIN_API_KEY | Yes | Your Devin API key | |
| DEVIN_BASE_URL | No | Base URL for the Devin API | https://api.devin.ai/v1 |
| DEVIN_ORG_NAME | No | Your organization name, defaults to "Default Organization" | Default Organization |
| SLACK_BOT_TOKEN | Yes | Your Slack Bot User OAuth Token (starts with xoxb-) | |
| SLACK_DEFAULT_CHANNEL | Yes | The default Slack channel where messages will be posted (channel ID or name) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_devin_sessionA | Create a new Devin session for code development and post the task to Slack. Note: This is the recommended approach as it will automatically post your task to Slack as @Devin mention. Please craft your request to Devin in the same language that the user is using to communicate with you, maintaining language consistency throughout the experience. |
| get_devin_sessionB | Get information about an existing Devin session and optionally fetch associated Slack messages |
| list_devin_sessionsC | List all Devin sessions |
| send_message_to_sessionA | Send a message to an existing Devin session and optionally to the associated Slack thread |
| get_organization_infoB | Get information about the current Devin organization |
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 5 tools
Each tool has a clearly distinct purpose with no ambiguity. create_devin_session initiates sessions, get_devin_session retrieves session details, list_devin_sessions enumerates sessions, send_message_to_session communicates with sessions, and get_organization_info provides organizational context. The boundaries between session management, communication, and organization info are well-defined.
All tools follow a consistent verb_noun pattern with snake_case throughout. The verbs (create, get, list, send) are appropriately descriptive and consistently applied, making the naming predictable and readable across the tool set.
With 5 tools, this server is well-scoped for managing Devin sessions and organization info. Each tool earns its place by covering essential operations: session creation, retrieval, listing, messaging, and organization details, without unnecessary bloat or missing functionality.
The tool set provides strong coverage for session lifecycle management (create, get, list, message) and organization info, with no dead ends. A minor gap exists in the lack of session deletion or update tools, but agents can likely work around this, and core workflows are well-supported.