Shipchart runs an MCP server at shipchart.app/mcp. This page covers how to connect a client, what the tools can read and write, and what you get on the free plan.
Once a client is connected, the assistant can look up revenue, goals, roadmaps and check-ins for any of your projects. It can also load a project's tech stack and conventions before it touches the code.
{
"mcpServers": {
"shipchart": {
"url": "https://shipchart.app/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}These are the tools you are likely to use most. Read tools work on every plan. Write tools need a paid plan and a token with the write ability. Deleting and triggering a sync need their own abilities. The full list is in the MCP docs.
| Tool | Description |
|---|---|
| dashboard_get | Portfolio summary: monthly revenue, project counts and stale projects |
| projects_list | Every project with its stage, tech stack and issue tracker |
| projects_get_context | What an agent needs before working on a project: stack, repo, deployment URLs, brief and notes |
| revenue_list | Revenue entries, filtered by date range or type |
| financials_summary | Revenue, expenses and profit for a month, compared with the month before |
| goals_list | All goals across the portfolio, with progress |
| roadmap_get | Roadmap items for one project or all of them |
| checkins_list | Recent check-ins with mood and notes |
| recent_errors | Recent errors from the Sentry or Bugsnag project you connected |
| Tool | Description |
|---|---|
| checkins_create | Record a check-in on a project, with a mood |
| revenue_create | Log a recurring or one-time revenue entry |
| expenses_create | Log a recurring or one-time expense |
| goals_create | Set a goal for one project or the whole portfolio |
| ideas_create | Park a new idea, with optional scores |
| roadmap_add | Add a roadmap item to a project |
| metrics_record | Record a value for a built-in or custom metric |
| update_project_context | Update a project's context fields (used by shipchart:discover-context) |
| delegate_to_agent | Hand a task to a runner you have set up and track it in Shipchart |
Ready-made workflows your client can run by name.
| Prompt | Description |
|---|---|
| shipchart:init | Run it inside a repo. Finds or creates the matching project, then fills in its context from the code |
| shipchart:discover-context | Re-reads the codebase and refreshes tech stack, architecture, conventions, features and limits |
| switch-project-prompt | Loads one project's full context and gives a short briefing |
| weekly-review-prompt | What changed this week, what needs attention and what to look at next |
| project-health-check-prompt | Revenue trend, activity and recommendations for one project |
| quick-capture-prompt | A quick round of check-ins across your active projects |
For clients that can attach MCP resources to a conversation.
| Resource | Description |
|---|---|
| founder://dashboard | A read-only snapshot of the whole portfolio |
| founder://projects/{id} | One project with revenue, links and recent check-ins |
| founder://projects/{id}/context | Developer context for a project, meant to be loaded at the start of a session |
Once the server is connected, any prompt that mentions your projects will work. These four are the ones worth saving. Copy one, paste it into your client and edit it to suit you.
| Prompt | What It Does |
|---|---|
| Weekly review | Reads the dashboard, goals and roadmap, then suggests what to work on first |
| Money check | Looks at revenue, expenses and profit and points out what changed |
| Roadmap critic | Reads a project roadmap and argues for what to cut or move |
| Friday wrap-up | Summarizes the week across projects and drafts check-ins for you to confirm |
Review my Shipchart portfolio for the week. Use the Shipchart tools to:
1. Read the dashboard and note any stale projects
2. Check active goals and their progress
3. Look at each roadmap for items that have not moved
4. Suggest what I should work on first, and say whyLook at the money across my Shipchart portfolio. Use the Shipchart tools to:
1. Get this month's financial summary
2. Compare revenue per project with last month
3. List my largest expenses
4. Tell me what changed and what deserves a closer lookAct as a skeptical product person. Use the Shipchart tools to:
1. Load the context for the project I name
2. Read its roadmap
3. Point out items that look too big or too vague
4. Suggest what to cut, split or move to LaterHelp me close out the week. Use the Shipchart tools to:
1. Summarize this week's check-ins and goal movement
2. List projects with no check-in this week
3. Draft a check-in for each and ask me to confirm before saving
4. Finish with a short plan for next weekIf you keep reusing a prompt, you can save it in Shipchart as a custom agent with its own instructions. Each one shows up in your MCP client as a prompt named agent:your-agent, and you can export it as a SKILL.md file. This part is optional.
The CLI reads the same data as the MCP server and can print it in a form a model can read. Like MCP, it is read-only on the free plan and can write on the Builder plan.
shipchart status prints revenue, goals, delegations and stale projectsshipchart delegate run hands a task to Copilot or your local workershipchart worker runs delegated tasks on your own machine and opens a pull request--format llm makes any command print compact markdown for a modelshipchart context export prints a project's context, ready to pipe or paste.shipchart.yml links a directory to a project, so commands know which one you meanshipchart/tap, or download a binary for macOS or Linux. The CLI docs have the exact commands. shipchart auth login. shipchart init. # Print this project's context and copy it
$ shipchart context export --size l | pbcopy
# Write it to AGENTS.md (and CLAUDE.md) in the repo
$ shipchart context pull --claude
# Any command, formatted for a model
$ shipchart roadmap list --format llmReading is free on every plan, for up to 4 projects. The Builder plan lets your assistant write as well.