Skip to main content
Glama
phenasdev

devin-mcp-bridge

by phenasdev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEVIN_MCP_AGENT_CMDNoAgent binary. Set to npx to bridge a different ACP agent.devin
DEVIN_MCP_AGENT_ARGSNoSpace-separated args.acp
DEVIN_MCP_PERMISSIONNoonce | all | denyonce
DEVIN_MCP_SANDBOX_FSNo0 disables the path guard.1
DEVIN_MCP_TIMEOUT_MSNoPer-turn cap; the turn is cancelled on expiry.900000

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
devin_taskA

Send a coding task to Devin (a separate autonomous coding agent) and return its full response. Devin keeps context across calls for the same working directory, so follow-up calls can refer to earlier work. Use for self-contained work you want done in parallel; state the task and the acceptance criteria explicitly, since Devin cannot ask you questions.

devin_resetA

Kill the running Devin agent and discard its conversation context. The next devin_task starts a fresh session. Use when Devin is stuck or the context is polluted.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one sends a task to Devin, the other resets the session. No overlap or confusion possible.

Naming Consistency4/5

Both tools use the 'devin_' prefix and snake_case, but the pattern is slightly inconsistent: 'devin_task' is a noun while 'devin_reset' is a verb. However, the prefix makes them clearly related.

Tool Count4/5

With only 2 tools, the server is minimal. For its purpose as a bridge to an autonomous agent, this is reasonable but slightly thin. A status or cancel tool could be added.

Completeness3/5

The server covers the basic workflow of sending tasks and resetting, but lacks features like checking task status or interrupting a running task. Some gaps exist but core functionality is present.

Maintenance

ActivityMaintained
ResponsivenessSyncing