Devin CLI MCP and history: connect tools and resume work

By CodeAgentSwarm · Updated September 11, 2026

MCP connects tools to an agent; history keeps the conversation you want to continue. They solve different problems. Set up one tool you trust, check that Devin can see it, then verify that the conversation can be reopened.

Inspect tools and saved sessions

bash

devin mcp list
devin list
devin -c

Use devin -c for the latest session in the current directory, or devin -r SESSION_ID for a specific session. Command reference.

Find the conversation before starting over

Devin conversations in the CodeAgentSwarm beta history — Real beta history capture. Select the original conversation to continue the same task.

In CodeAgentSwarm beta, Devin conversations are available through history, search and bookmarks. A saved shortcut can reopen the associated conversation. Check the project and previous messages when resuming so your next request has the intended context.

Choose where an MCP server belongs

Scope	Configuration file
Local	`.devin/mcp_config.local.json`
Project	`.devin/mcp_config.json`
User	`~/.config/devin/mcp_config.json` / `%APPDATA%\devin\mcp_config.json`

Use local scope for configuration specific to your checkout and project scope only for settings suitable for sharing. The current CLI uses dedicated MCP files. Official MCP configuration.

bash

devin mcp add docs https://your-mcp-server.example/mcp
devin mcp list

Replace the example URL with the endpoint of a server you trust. It is a placeholder, not a hosted service. Authenticate with that server if required and check its exposed tools before asking Devin to use them.

CodeAgentSwarm MCP is optional

The beta can connect Devin to CodeAgentSwarm tools for supported session and workspace actions. The app setting controls this integration. If you turn it off, new Devin launches should respect that choice; do not add it back manually just to make a test request work.

Installing a server and authorizing one of its actions are separate decisions. Read the action and target before allowing a change, especially when a tool can modify a remote service.

Verify resume with a small question

Ask Devin to identify the test command in your sample project.
Close the conversation after its answer is complete.
Reopen it from history and ask which command it found.
Confirm that the original messages and project still match.

If the session is absent on Windows, check the native history location. If it opens but cannot run a new turn, inspect authentication and quota separately from the saved transcript.

Devin in CodeAgentSwarm: beta status

The integration is being tested for an upcoming CodeAgentSwarm release. The screenshots show that beta, not a promise that the current public installer already includes Devin. Sign in with the official Devin CLI on the computer that runs the agent.

FAQ

Resume targets the saved session. Verify its project and earlier messages before continuing, especially if you have several similar tasks.

No. The CodeAgentSwarm MCP integration is optional in the beta. Devin also supports its own MCP configuration.

No. Keep personal secrets out of shared project configuration and use the appropriate local or account authentication mechanism.

Devin Chat, installation and history are in CodeAgentSwarm beta testing for an upcoming release. The button downloads the current public app; check its release notes for Devin availability.

Download free betamacOS & Windows

Devin CLI: installation, login and your first coding task

Devin CLI brings a coding agent to your local project. Start with a small task, verify that it can read the right files, and keep the resulting conversation for the next step. This guide covers the standalone CLI and the upcoming CodeAgentSwarm integration.

Read guide

View all guides