Prompts and resources
The guided prompts and reference resources the FounderSync MCP server offers, and example requests to try.
Besides tools, the FounderSync server offers guided prompts and two reference resources. Prompts are ready-made starting points for common jobs. Resources are documents your agent can read to use the tools correctly.
Guided prompts#
A prompt does not run anything by itself. It gives your agent a step-by-step plan that uses the right tools in a sensible order, and tells it what to ask you first. How you pick a prompt depends on your client: many show them in a menu or as commands, and some do not show prompts at all. If yours does not, you can ask for the same thing in plain words, as in the examples below.
| Prompt | What it does | Options |
|---|---|---|
setup_startup | Turns a rough idea into a set-up workspace: idea, PRD, roadmap tasks, launch checklist and a note about the cofounder agreement. | idea |
plan_launch | Finds gaps in your launch checklist and creates tasks to close them. | target_date as YYYY-MM-DD |
setup_cap_table | Creates share classes, stakeholders, founder shares, the option pool and any SAFEs. | total_founder_shares |
prepare_fundraise | Models the round, shows dilution and exit payouts, and checks what investors ask for. | amount, pre_money |
weekly_review | Summarizes what moved, what is stuck, what is due and what needs a decision. | none |
draft_cofounder_agreement | Walks you through each agreement section and saves it. Full-access endpoint only. | context |
All options are optional.
What to expect#
- setup_startup checks what already exists, asks up to five short questions for facts it cannot infer, then fills in the idea, writes an MVP-scoped PRD, creates 15 to 30 tasks and sets up the launch checklist.
- plan_launch marks checklist items that are already true as done and creates tasks working back from your target date.
- setup_cap_table imports founder shares from the cofounder agreement when one exists, so the two agree, and asks about the option pool and any SAFEs.
- prepare_fundraise runs round scenarios and exit waterfalls and creates tasks for gaps. It does not close a round.
- weekly_review only reads. It changes nothing without asking.
- draft_cofounder_agreement saves one section at a time, marks it configured only after the founders confirm, and never signs or verifies identity. It is a starting point, not legal advice.
On the read-only endpoint, draft_cofounder_agreement is not offered. The other prompts are listed, but their steps that save changes cannot run there.
Example requests#
- "Set up my idea and PRD. The idea is a scheduling tool for dental clinics."
- "Plan my launch for 2026-12-15."
- "Set up my cap table. We hold 10,000,000 founder shares together."
- "Help me prepare to raise 1.5M at an 8M pre-money valuation."
- "Give me my weekly review."
- "Draft our cofounder agreement. We already agreed an equal split."
Resources#
Resources are read-only documents your agent can open. Most clients let you attach them or let the agent read them on its own.
| Resource | URI | Contents |
|---|---|---|
| FounderSync MCP guide | foundersync://guide | Markdown: how the workspace is organized and how to work with it well. |
| Valid values | foundersync://reference/enums | JSON: every value a tool accepts. |
The guide explains that ids are UUIDs and dates are YYYY-MM-DD, what each area covers, and some working habits: start with whoami and get_startup_overview, prefer batch tools, ask before large changes, and do not invent facts about the company.
The valid values resource lists allowed values for task status, priority and domain, startup stage, contribution types, vault categories, cap table kinds and more. If an agent passes a wrong value, point it at this resource.
The server also sends a short instruction text when a client connects, which tells the agent to call whoami and get_startup_overview first and that destructive tools require confirm: true. See the tools reference and security and access.