MCP tools reference

get_workspaceread#

Who am I and what's here: workspace name, timezone and today's date, your scopes and agent name, every round with its stage keys, and the allowed investor types and activity kinds. Call this first.

No parameters.

Returns{workspace: {id, name, slug, is_sandbox, timezone, today, weekday, default_currency}, you: {agent_name, scopes, key_prefix}, rounds: [{id, slug, name, status, currency, target_amount, stages: [{key, label, kind}]}], investor_types, loggable_activity_kinds}

list_roundsread#

List fundraising rounds with target, committed amount and participant counts per stage kind. Use the slug or name as round in other tools.

Returns{rounds: [{id, slug, name, status, instrument, currency, target_amount, committed_amount, target_close_on?, counts: {total, open, active, won, lost}}]}

create_roundwriteidempotent#

Create a fundraising round with the default stages (New, Researching, Contacted, Replied, Meeting, Diligence, Committed, Passed). Safe to repeat: if a round with this name exists, it is returned unchanged with created: false. Returns the round with its stage keys, ready for add_investor / add_to_round.

Returns{created, round: {id, slug, name, status, instrument, currency, target_amount, stages: [{key, label, kind}]}}

get_round_summaryread#

The state of a round in one call: committed vs target, soft-circled and weighted pipeline, investors per stage, overdue and upcoming follow-ups, stale conversations (no activity for 14+ days), recent activity and warnings. Use it for status updates and 'what should I do today'.

ReturnsRoundSummary: {round, money: {currency, target, committed, pct_of_target, soft_circled, weighted_pipeline, committed_count}, funnel, counts, follow_ups: {overdue, today, next_7_days, top}, stale, recent_activity, warnings}

search_investorsread#

Find investors. query matches name, firm, title, email, location, tags, industries, source and notes (all words must match). Without round, it searches all workspace contacts and shows each one's stage in every round. With round (or any of stage/fit_min/follow_up, which imply the single open round), it returns investors in that round with stage, fit, follow-up and amounts.

Returns{round?: {slug, name}, results: [investor + stage, fit, priority, follow_up_on, amounts (in a round) or rounds: [{round_slug, stage_key, fit}]], next_cursor?, total}

get_investorread#

Everything about one investor: contact fields, notes, their stage and terms in every round, and the timeline (newest first) with who did what, including agent actions.

Returns{investor, participations: Participant[], timeline: Activity[], timeline_truncated}

add_investorwriteidempotent#

Add an investor contact, or find the existing one and fill in what it is missing. Dedupes by email, then LinkedIn profile, then name+firm, then the name alone when there is exactly one person with that name; matched_on tells you which. on_duplicate: fill_empty (default: fill empty fields, merge tags, and append new notes as a dated paragraph; it never overwrites), return_existing (change nothing; not_applied lists the fields you sent that were not saved), create_anyway (ignore name matches; email/LinkedIn duplicates are never created). Pass round (and optionally stage, fit, follow_up_on, follow_up_note, next_step, amount_soft) to also put them on that round's board in the same call. Leave unknown fields out.

Returns{investor, created, matched_on?: email | linkedin | name_firm | name, filled_fields?, not_applied?, hint?, round?, participant?, warning?}

{"name": "Dana Whitfield", "firm": "Harbor Light Ventures", "email": "dana@example.com", "type": "vc", "round": "seed", "stage": "research", "fit": 4}

add_investorswriteidempotent#

Add up to 50 investors in one call, each exactly as add_investor would (same dedupe and on_duplicate rules), optionally all on one round. Each item takes add_investor's contact fields plus its own stage, fit, follow_up_on, follow_up_note, next_step and amount_soft. Returns one compact line per item (id, name, created or matched_on, and any error), so one bad item does not stop the rest.

Returns{counts: {created, existing, errors}, results: [{item, id, name, created, matched_on?, not_applied?, stage?, error?}]}

update_investorwrite#

Change an investor's contact fields. Only keys in set change; null clears a field. Use add_tags/remove_tags to edit tags without rewriting the list, and append_notes to add a dated paragraph to their notes instead of replacing them. Round-specific fields (stage, fit, follow-up, amounts) are changed with add_to_round, move_stage, set_follow_up and record_commitment.

Returns{investor, changed_fields} (an empty list means nothing changed and nothing was logged)

add_to_roundwriteidempotent#

Put an investor on a round's board, or update their round fields if they are already there. Safe to repeat. New participants start in the first stage unless you pass stage. For an existing participant, a different stage moves them (logged as a stage change).

Returns{participant, created, changed}

move_stagewriteidempotent#

Move an investor to another stage in a round (for example contacted → meeting). Moving to the current stage does nothing. Add note to explain why; it appears on the timeline. To mark a commitment with an amount, use record_commitment instead of moving to the won stage.

Returns{participant, changed, from, to}. Errors: not_in_round (use add_to_round), stage_not_found (lists valid keys).

log_activitywrite#

Record something that happened with an investor: a note, an email (sent or received), a call or a meeting. body is what happened in plain words. occurred_at defaults to now; past dates are fine, and a future meeting time records a scheduled meeting. Pass round when it concerns a specific round. Pass a stable idempotency_key (for example an email message id) to make retries safe.

Returns{activity, duplicate}

set_follow_upwriteidempotent#

Set or clear the date you should next follow up with an investor in a round. Give exactly one of on (YYYY-MM-DD), in_days (from today in the workspace timezone) or clear: true. note says what the follow-up is for (shown in the follow-up list).

Returns{participant, changed}

list_due_follow_upsread#

Follow-ups that are due: overdue first, then today, then (with within_days > 0) the next N days. Without round, it covers all open rounds. Use it to plan the founder's outreach for the day; for 'this week', pass within_days=7. counts always includes next_7_days and next_due_on, so an empty list never hides a busy week ahead.

Returns{today, weekday, items: FollowUpItem[], counts: {overdue, today, upcoming, next_7_days, next_due_on?}}

record_commitmentwriteidempotent#

Record that an investor committed money to a round. amount is the total commitment in whole currency units (it replaces any earlier amount; it is not added to it), and 0 clears it. By default this also moves them to the round's won stage (Committed) and adds them to the round if needed.

Returns{participant, previous_amount?, moved_stage, round_committed_total}

import_investors_csvwrite#

Import investors from CSV text (first row = headers). Columns are auto-mapped from common headers (Name, Firm/Fund/Company, Email, LinkedIn, Type, Check size, Tags, Stage, Fit, Follow up…); pass mapping to override ({"Column header": "field" or null to ignore}). Existing investors are matched like add_investor. dry_run defaults to true and returns a preview with counts and per-row actions; show it to the human, then call again with dry_run=false. With round, imported investors are added to that round, and the stage, fit, follow-up and amount columns apply.

ReturnsDry run: {counts, mapping, warnings, rows} where rows lists only updates, skips, errors and rows with warnings (plain creates are counted). Otherwise: {import_run_id, counts, errors, created: [{row, id, name}]}.

export_roundread#

Export a round's pipeline: every investor in the round with contact fields, stage, fit, follow-up, amounts and last activity date. format=csv gives spreadsheet-ready text; json gives structured data. Set include_activities to add each investor's timeline (json only).

Returns{round: {slug, name}, format, filename, row_count, content}. Over 1 MB: payload_too_large with the REST URL to use.