Agentic PM — MCP + BYOK
Two integration points connect DeveloSaur to your AI workflow. MCP lets your external agent edit your project graph directly. BYOK lets the in-app AI Chat run on your own API key. Use one, the other, or both — they do not conflict.
MCP — three-step setup (Pro tier)
- Download .develosaur.json from the project card in the project list — the file is scoped to that one project and contains a bearer credential (dsk_*).
- Place .develosaur.json in your project root (same folder as package.json or pyproject.toml).
- Run `npx @develosaur-ai/mcp@latest init` once. The init command creates/updates .mcp.json, adds .develosaur.json to .gitignore, installs Claude slash commands into .claude/commands/, and verifies the connection.
- Slash commands installed: /develosaur-work, /develosaur-plan, /develosaur-sync, /develosaur-collaborate, /develosaur-review, /develosaur-setup.
- Around 30 MCP tools available: get_tree, find_nodes, add_child, batch_create_nodes, complete_node, gather_context (GraphRAG), find_similar (semantic search), find_decisions, get_priority_order, suggest_unblocked_next, get_sprint_summary, develosaur_sitrep, and more.
- Auth flow: the bearer credential is exchanged for a short-lived JWT against the exchange-mcp-key edge function on each session start. The JWT is never persisted to disk.
- Works with Claude Code, Cursor, Continue, Cline, and any MCP-compatible client. Slash commands are Claude Code specific.
- Requires a Pro subscription. The exchange endpoint returns 403 for non-Pro accounts.
BYOK — bring your own AI key
- The in-app AI Chat (HeatBot) runs on your provider key. Supported: Anthropic (claude-sonnet-4-6 default), OpenAI (gpt-4o), Groq (llama-3.3-70b-versatile), DeepSeek (deepseek-chat), xAI (grok-2-latest), OpenRouter, or any OpenAI-compatible Custom endpoint.
- Settings → AI Providers — pick a provider tile, paste your key, optionally change model and base URL. A Test button validates the key with a real 1-token request before save.
- Keys live in browser localStorage under develosaur-ai-providers. They never persist on DeveloSaur servers — they flow through the collaborate edge function to your provider in-flight only, then evaporate.
- No rate limits from us. You pay your provider directly. Save multiple configs (e.g., Work Anthropic, Personal Groq) and switch the active one in Settings.
- Multi-device: keys live on the device that entered them. They do not sync across browsers — by design, since they never touch a server.
- Works on every plan including Dry Run — no account required. Cloud projects unlock embeddings-powered semantic retrieval so the chat focuses on the most relevant nodes.
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, run sprint sitreps.
- BYOK — when you want a side-panel Chat that sees your whole project graph and you prefer the in-app conversational flow over external agent commands.
- Use them together. The MCP agent and the in-app Chat both operate on the same project graph.
Try DeveloSaur Free
Related
Please enable JavaScript to use the full DeveloSaur application.