Devplan for Claude

Your whole product brain in Claude. One connection.

Q: How do I connect Devplan to Claude Code?

Run claude mcp add --transport http devplan-remote https://app.devplan.com/api/v1/mcp, then complete the authorization in your browser: pick your Devplan workspace and choose Authorize. See the MCP setup guide.

Q: Does it work with Codex, Cursor or other AI clients?

Yes. Codex connects with codex mcp add, and any client that supports remote HTTP MCP servers can add the same URL: https://app.devplan.com/api/v1/mcp.

Your AI product manager inside Claude. Devplan's knowledge graph links customer feedback, decisions, code and delivery. Connect it once, and Claude can plan, answer, brief and build with all of it.

Start free Talk to a Human

$100 in free credits. No card.

Claude

Before we plan exports, check why we're building it and what customers expect.

Devplan search_entities “exports”

Found 12 customer requests, 1 project, 2 decisions

Devplan fetch_internal_entities_by_ids 3 records

Read 3 records

12 customers asked for faster reports and exports, mostly finance teams closing the month. What they expect:

Choose which columns to export 8 customers
Exports that finish in under a minute 5 tickets
No PDF export this quarter decision, Sep 12

I'd plan column selection first and skip PDF. Want me to draft the spec?

Summarize recent customer feedback about onboarding and cite the evidence.

Devplan search_entities “onboarding feedback”

Found 9 requests across support tickets and sales calls

Three themes, by number of customers:

Setup takes too many steps 5 customers
Invites get lost in spam 3 tickets
No sample data to try things 2 sales calls

Each theme links back to the tickets and calls in Devplan.

We're changing billing. Which product decisions should we respect?

Devplan query_workspace_graph topic: billing

2 decisions, 1 open customer request

Two decisions apply here:

Annual plans keep their price until renewal decision, Sep 18
No new payment provider this quarter decision, Oct 2

Both should go in the spec, and the payment provider stays as it is.

Catch me up on this week: what changed, what's at risk, what needs attention?

Devplan query_workspace_graph last 7 days

14 customer requests, 2 decisions, 3 releases, 1 risk

Your week:

14 new customer requests, most about faster exports support · sales calls
Shipped 3 features that 21 customers asked for GitHub · 9 PRs
Risk: billing work waits on another team's API, 2 days late project plan

Needs attention: tell the 21 customers, and decide on the billing date.

Try a prompt, or open the Devplan connector to see its tools

Works in Claude Code today. The Claude desktop app is coming soon.

Used by fast-moving teams

Video · 0:27

Connect Claude Code in one command.

One command, over MCP
Claude Code checks customer requests and decisions
Project status, right in your terminal

Start free All videos →

The knowledge graph

Everything Devplan knows, in Claude.

Devplan turns your tools into one knowledge graph: each request linked to its customer, deal, decision and code. One connection gives Claude all of it.

Connected, not searched

A request already knows its customer, the deal it affects, the decision about it and the code that shipped it.

Kept up to date

New tickets, calls, messages and commits keep flowing into the graph from the tools you connect.

Every fact has a source

Claude can cite the ticket, call or decision behind each answer, so you can check it.

How the graph works: Product brain

One command

Connect once. Claude gets the why.

Start free and connect where customer feedback and work live: support, CRM, GitHub, Jira or Linear.
Run one command in your terminal.
Approve in the browser and pick your Devplan workspace. Done.
Optional: add the Devplan skills for ready-made product workflows (below).

Read the MCP setup guide →

$ claude mcp add --transport http devplan-remote https://app.devplan.com/api/v1/mcp

$ codex mcp add devplan-remote --url https://app.devplan.com/api/v1/mcp
$ codex mcp login devplan-remote

https://app.devplan.com/api/v1/mcp

Add this URL as a remote HTTP MCP server in Cursor or any client that supports it.

✔ Then ask: “Use Devplan to list projects in this workspace.”

Devplan skills

Then add the Devplan skills.

20 open-source skills for Claude Code and Codex. Start with one that makes your agent Devplan-aware on its own, or install all of them for ready-made product workflows.

Works withClaude CodeCodex

Recommended: make your agent Devplan-aware

$ npx skills add devplaninc/devplan-skills --skill devplan-product-context

All 20 skills

$ npx skills add devplaninc/devplan-skills --skill '*'

Needs a Devplan workspace and the Devplan MCP connected first.

devplan-product-contextQuietly adds current Devplan context to everyday product and engineering questions.
brief-with-devplanA product pulse: what changed, what's at risk, what needs attention.
plan-with-devplanAn evidence-backed plan from customer demand, decisions, current work and risks.
estimate-with-devplanRemaining effort and time, from scope, similar past work and capacity.
customer-release-briefLinks what shipped to who asked, and drafts customer updates for review.
product-answer-verifierChecks a claim before you tell a customer, and rewrites it into safe wording.

See all 20 skills on GitHub →

Faster and cheaper

One call instead of searching everything.

Without Devplan

> why are customers asking for faster exports?

⏺ Search GitHub…

⏺ Search Jira…

⏺ Search Slack…

⏺ Read Notion pages…

⏺ Search support tickets…

… still piecing it together

With Devplan

> why are customers asking for faster exports?

⏺ devplan-remote - search_entities (MCP)

⎿ 12 requests, linked to customers, deals and a decision

⏺ 12 customers, mostly finance teams closing the month…

Up to 6x faster

1m 42s vs 9m 57s to answer the same question: Claude with Devplan's MCP, versus Claude connected to each tool directly.

Up to 4.5x lower model cost

$1.16 vs $5.38 for that same answer, because Devplan hands Claude the evidence instead of making it search every tool.

No re-explaining

Stop pasting the same background into every prompt. Claude looks it up when it needs it.

Less rework

Building from customer evidence and past decisions means fewer wrong turns. See our planning test

From one side-by-side test in our demo video. Results vary with the question and your data.

Same prompt, different result

Claude Code knows your code. Devplan tells it why.

Claude Code alone

> add CSV export to reports

⏺ I'll add an Export button that downloads every column as CSV. I can add PDF too.

Builds what the ticket says
Misses what customers need
Breaks a decision nobody told it about

Claude Code with Devplan

> add CSV export to reports

⏺ devplan-remote - search_entities (MCP)

⏺ 8 of the 12 customers who asked need to pick columns, and PDF is ruled out this quarter. I'll build the column picker first.

Starts from what customers asked for
Respects past decisions
Cites the evidence so you can check it

Ask it before you build it.

> summarize recent customer feedback about onboarding
> find projects related to billing and explain what's unfinished
> check for product decisions before editing this feature
> who asked for this, and why?
> what's left on this project?

> explain what this capability does, then compare it with the code
> which customers are waiting on this fix?
> what did we decide about pricing last month?
> draft the acceptance criteria from customer requests
> what changed since the last release?

Not just for code

Useful to everyone who works on the product.

The same connection answers product, customer and delivery questions, not only coding tasks.

Product managers

> plan this feature using the customer demand, related decisions, current work and risks

> which important customer needs are still unaddressed?

Sales and customer success

> what has this customer asked for, and what did we ship for them?

> can we safely tell this customer the feature is available today?

Founders and leads

> what changed across the product since yesterday, and what's at risk?

> where are we investing without strong customer demand?

What Claude can look up

Your product context, one tool call away.

search_entities

Customer feedback

Requests from support, sales calls and Slack, counted by customer and deal.

query_workspace_graph

Decisions and the why

What was decided, when, and the evidence behind it.

list_workspace_projects

Projects and status

What's planned, what's done and what's at risk.

fetch_external_documents

Connected docs

Specs and notes from the tools you connected to Devplan.

Make it a habit

Add a few lines to CLAUDE.md.

Paste this into your CLAUDE.md or AGENTS.md, next to your other rules, and Claude checks Devplan whenever a task depends on product context.

CLAUDE.md

Use Devplan when a task depends on product context,
customer feedback, project status, internal decisions,
or evidence across connected sources.
Check the tools available in this session and retrieve
relevant evidence. Use local code to verify
implementation details. Distinguish planned,
implemented, deployed, and enabled behavior.
Cite supporting sources and state material uncertainty.

In your control

Context in, nothing taken for granted.

You pick the workspace

You choose which Devplan workspace Claude Code can use when you authorize the connection.

Sources you can check

Answers cite the tickets, calls and decisions they came from, so you can verify before you rely on them.

You review the work

Claude Code proposes; you review its conclusions and changes, as you do today.

OAuth or an API key

SOC 2 Type II

Data is encrypted in transit and at rest, and Devplan never trains models on your data.

No per-seat pricing

One shared credit pool for the whole team, starting with $100 free.

Questions

Devplan for Claude, answered

How do I connect Devplan to Claude Code?

Run claude mcp add --transport http devplan-remote https://app.devplan.com/api/v1/mcp, then complete the authorization in your browser: pick your Devplan workspace and choose Authorize. See the MCP setup guide.

What is MCP?

MCP, the Model Context Protocol, is how Devplan connects to Claude Code: it's a standard for linking AI clients to tools and data. Devplan runs a remote MCP server, so Claude Code can use your workspace context without you pasting it into every prompt.

Does it work with Codex, Cursor or other AI clients?

Yes. Codex connects with codex mcp add, and any client that supports remote HTTP MCP servers can add the same URL: https://app.devplan.com/api/v1/mcp.

What can Claude Code see in Devplan?

The workspace you authorize: customer feedback, decisions, projects and documents from the tools you connected to Devplan. Some tools can start planning or update content, depending on how your workspace is set up, so review what Claude proposes.

What are the Devplan skills?

Devplan skills are 20 open-source workflows for Claude Code and Codex, such as a product pulse, an evidence-backed plan or a customer release brief. Install them with npx skills add devplaninc/devplan-skills after connecting the Devplan MCP. See them on GitHub.

Is Devplan in Claude Code only for coding?

No. Devplan brings your whole product knowledge graph into Claude Code, so you can also plan features, check what customers asked for, get a weekly product pulse or verify what's safe to tell a customer.

Do I need to be a developer to use it?

No. Product managers use Claude Code to ask about customers, decisions and projects without writing code. Read Claude Code for product managers.

What does it cost?

Devplan starts with $100 in free credits, valid for 3 months, with no card. After that you buy credits for one shared pool, with no per-seat charge. See pricing.

Give Claude the why.

$100 in free credits. No card.

Start free Talk to a Human