MissionD is a daemon and tool surface that turns requests into reviewed Lisp artifacts, approved plans, BoardTasks, and worker execution. The V3
Connect Missiond to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MissionD is a daemon and tool surface that turns requests into reviewed Lisp artifacts, approved plans, BoardTasks, and worker execution. The V3 control-plane authority is .missiond/v3/missiond-blueprint.lisp; generated JSON under. The missiond mcp server is what makes that connection.
The server ships on npm as @missiond/core, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Core — The Core tool exposed by this serverMonitoring — The Monitoring tool exposed by this serverPermissions — The Permissions tool exposed by this serverInfrastructure — The Infrastructure tool exposed by this serverConfiguration is passed through the environment: MISSION_LOG_LEVEL, MISSION_PG_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Missiond's toolset — Core, Monitoring, Permissions and 1 more — is a fair guide to whether it matches your workflow. It is maintained by rickyjim626; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Core | The Core tool exposed by this server. |
| Monitoring | The Monitoring tool exposed by this server. |
| Permissions | The Permissions tool exposed by this server. |
| Infrastructure | The Infrastructure tool exposed by this server. |
{
"mcpServers": {
"mission": {
"command": "mission-mcp",
"args": [],
"env": { "MISSION_LOG_LEVEL": "warn" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MISSION_LOG_LEVEL | Configuration value read at startup. | Optional |
| MISSION_PG_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.