Devplane Site is an MCP server with 4 tools an agent can call, among them get_faq, list_comparisons, list_faqs. It answers at https://devplane.dev/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Read-only MCP access to devplane.dev's public pages, FAQ corpus and comparisons.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_faq | Get one FAQ entry by slug (from the list_faqs catalog), e.g. what-is-multi-agent-orchestration. Inputs: slug |
list_comparisons | List every comparison from https://devplane.dev/compare — DevPlane vs. a single AI assistant, vs. an issue tracker, and multi-agent vs. single-agent — each with the full side-by-side dimension table and verdict. |
list_faqs | List every question/answer pair from https://devplane.dev/faq — 10 questions on multi-agent orchestration, operator cockpits, diagnosis, and comparisons, answered directly. |
list_pages | List devplane.dev's public, crawlable marketing pages (home, explain, compare, faq) with route, canonical URL, title and description. Excludes the secret-gated internal editor. |
Every block below points at https://devplane.dev/api/mcp. Pick your client and copy.
claude mcp add --transport http devplane-site https://devplane.dev/api/mcp
{
"mcpServers": {
"devplane-site": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://devplane.dev/api/mcp"]
}
}
}{
"mcpServers": {
"devplane-site": {
"url": "https://devplane.dev/api/mcp"
}
}
}{
"servers": {
"devplane-site": {
"type": "http",
"url": "https://devplane.dev/api/mcp"
}
}
}{
"context_servers": {
"devplane-site": {
"url": "https://devplane.dev/api/mcp"
}
}
}{
"mcpServers": {
"devplane-site": {
"serverUrl": "https://devplane.dev/api/mcp"
}
}
}{
"mcpServers": {
"devplane-site": {
"url": "https://devplane.dev/api/mcp"
}
}
}name: Devplane Site
version: 0.0.1
schema: v1
mcpServers:
- name: Devplane Site
type: streamable-http
url: https://devplane.dev/api/mcp{
"mcpServers": {
"devplane-site": {
"httpUrl": "https://devplane.dev/api/mcp"
}
}
}{
"mcpServers": {
"devplane-site": {
"type": "http",
"url": "https://devplane.dev/api/mcp"
}
}
}{
"mcpServers": {
"devplane-site": {
"url": "https://devplane.dev/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fdevplane.dev%2Fapi%2Fmcp&type=streamable_http&id=devplane-site&name=Devplane%20Site
It answered our last check on 19 October 2026 in 195 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by devplane.dev and served from devplane.dev, the vendor's own domain: https://devplane.dev/api/mcp.
4, as returned by the server's own tools/list on 11 September 2026: get_faq, list_comparisons, list_faqs, list_pages.
It answered our last check on 19 October 2026 in 195 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://devplane.dev/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.devplane. Endpoint host: devplane.dev. ARD identifier: urn:air:dev.devplane:mcp:devplane-site.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.