Agentic PM — MCP + REST
Two roads connect your AI workflow to the same live graph. MCP gives compatible clients the full tool surface. Plain REST covers every other agent, taught by one llms.txt. Both edit the same board, at the same time if you like.
MCP — one paste
- Paste one sentence to your agent: "Read https://mcp.develosaur.com/llms.txt and use it to build me a develosaur board for my project". Or add the gateway wherever your client takes an MCP server URL: claude mcp add --transport http develosaur https://mcp.develosaur.com/v1/mcp.
- No account to try it — the gateway mints a live trial board and returns a link you can open to watch it build.
- To work on your own boards the agent authorizes itself: it shows a short code, you approve it in your browser, and it continues in the same conversation. Every connected agent is revocable in Settings.
- 17 MCP tools, one obvious verb per intent. Read: review_tree, read_nodes, find, gather_context. Write: grow, create_nodes, update_nodes, complete_nodes, move_nodes, archive_nodes, delete_nodes. Graph and ordering: edges, prioritize. Project and meta: tags, projects, capture.
- Works with Claude Code, Cursor, Continue, Cline, and any MCP-compatible client. Claude Code additionally gets six slash commands.
- Available on every plan, including Free — paid tiers only raise your project count.
REST — bring your own agent
- No MCP in your harness? Every graph operation is also a plain REST route, and https://mcp.develosaur.com/llms.txt teaches any agent the whole surface.
- Covers open models in local harnesses (DeepSeek, Kimi, Qwen through Ollama, LM Studio, vLLM), homegrown CLI agents and scripts, and any framework with an HTTP tool.
- Sign-in without secrets: the agent requests a short code, you approve it in your browser. It never asks you for a password or an API key.
- Anonymous sandboxes are isolated — a sandbox connection can never reach a real account’s projects.
When to use which
- MCP — when you are coding in Claude Code or Cursor and want the agent to drive the project: create nodes, set ranks, mark completions, walk dependencies.
- REST — when your agent or harness has no MCP support, or you want automation: a cron job that files captures, a CI step that marks nodes complete.
- Use them together. An MCP client and a REST agent both operate on the same project graph, at the same time — CRDT merge means nothing conflicts.
Try DeveloSaur Free
Related
Please enable JavaScript to use the full DeveloSaur application.