Integrates Claude AI capabilities with Plane project management for enhanced automation and collaboration.
Claudeus Plane MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Integrates Claude AI capabilities with Plane project management for enhanced automation and collaboration.
This is a private repository for SimHop IT & Media AB team members only. While the code is available for viewing and use under the MIT license, we do not accept public contributions at this time. You are welcome to fork the repository and create your own version, as long as it's not identical or extremely similar to our package to avoid user confusion.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Claudeus Plane is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — The Configuration tool exposed by this serverAuthentication — The Authentication tool exposed by this serverTroubleshooting — If the server isn't showing up in Claude: 1. Verify your claude_desktop_config.json syntax 2. Ensure file paths are absolute and valid 3. CheckYou will need one environment variable: PLANE_INSTANCES_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
## Before you rely on it
- Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
- MCP clients confirm each tool call by default. Leave that on until you have watched what the claudeus plane mcp server does with a few real requests.
## Choosing this one
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Claudeus Plane's toolset — `Prerequisites`, `Installation`, `Configuration` and 2 more — is a fair guide to whether it matches your workflow. It is maintained by deus-h; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Claudeus Plane's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
| Authentication | The Authentication tool exposed by this server. |
| Troubleshooting | If the server isn't showing up in Claude: 1. Verify your claude_desktop_config.json syntax 2. Ensure file paths are absolute and valid 3. Check Claude's logs at: - macOS: ~/Library/Logs/Claude - Windows: %APPDATA%\Claude |
#### Docker Setup 🐳
```json
{
"mcpServers": {
"claudeus-plane-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"--mount", "type=bind,src=/absolute/path/to/your/plane-instances.json,dst=/app/plane-instances.json",
"--mount", "type=bind,src=/absolute/path/to/your/.env,dst=/app/.env",
"mcp/plane",
"--config", "/app/plane-instances.json"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PLANE_INSTANCES_PATH | Filesystem location the server is allowed to use. | Optional |
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.