Labsco
MCP SERVER

ProposalCraft

by jabbawocky

Draft freelance proposals in your own voice from your past winning work — plus the client emails around them, from first brief to project closure.

Marketing Automation & AdvertisingVerified
Summary
Feed it your winning proposals first — that is where the voice comes from.

Drafting from scratch gives you a generic proposal; drafting against your saved examples is what makes it sound like you wrote it, and the bundled templates are only a starting point until you add your own. `analyze_brief` is the one to reach for before drafting: it costs nothing against the monthly limit and its job is to tell you whether to quote at all.

What it is

A proposal and client-communication toolkit for freelancers and consultants. You save proposals that won, and it drafts new ones using them as voice and format references. Around that sit the emails the job actually needs: follow-ups, change orders, kickoffs, status updates, rate increases, offboarding.

What you get
  • A brief analysed before you commit: budget signals, timeline signals, red flags, scope-creep risks, the questions to ask, and a go/no-go call — `analyze_brief`
  • A full proposal drafted from a brief using your saved examples for voice, plus retainer and reduced-scope variants — `draft_proposal`, `retainer_proposal`, `budget_proposal`
  • A draft critiqued with specific rewrites for the weak sections — pricing, hook, why-me, scope — and distilled into a pitch email of 150 words or fewer — `improve_proposal`, `proposal_to_email`
  • Accepted work formalised: a statement of work, a change order for out-of-scope requests, an NDA and a freelance services agreement in plain English — `scope_of_work`, `change_order`, `nda_template`, `contract_template`
  • The awkward emails written for you: chasing silence, warning about a slipping deadline, apologising for a missed one, holding your rate when asked for a discount, announcing a rate increase, escalating an overdue invoice — `client_followup`, `project_delay_warning`, `late_delivery_apology`, `discount_request_response`, `rate_increase_email`, `invoice_reminder`
  • Project rhythm covered end to end: onboarding checklist, kickoff, deposit request, status updates, mid-project check-ins, pause and restart, closure and annual review — `client_onboarding_checklist`, `project_kickoff_email`, `deposit_request_email`, `project_status_update`, `project_pause_email`, `project_restart_email`, `project_closure_email`
  • Business development: cold pitches, reactivation notes, referral and testimonial requests, upsells, partnership outreach, LinkedIn posts and case-study outlines — `cold_pitch`, `reactivation_email`, `referral_request`, `testimonial_request`, `upsell_email`, `partnership_outreach`, `linkedin_post`, `case_study_outline`
  • A local reference library you own: save, list, read and delete proposals — `save_proposal`, `list_proposals`, `get_proposal`, `delete_proposal`, `usage_status`
Requirements

Node.js 18+ and Claude Desktop or Claude Code. No API key — it runs on your existing Claude session. Installed with `npx -y github:jabbawocky/proposalcraft` or as a Claude Code plugin. Proposals are stored locally under `~/.proposalcraft/proposals/`, and `PROPOSALS_DIR` points that at a synced folder instead. The free tier allows 5 `draft_proposal` calls per month and resets on the 1st; Pro is $19/mo for unlimited drafts. Twelve bundled starter templates ship with it.

Setup effort

One command — npx -y github:jabbawocky/proposalcraft