Proposalcraft

What jabbawocky/proposalcraft MCP server does

The jabbawocky/proposalcraft MCP server supports a proposal workflow for freelancers and consultants. It can inspect a new client brief, identify budget and timeline signals, flag scope risks, suggest clarifying questions, and provide a go/no-go recommendation before work begins.

After you have reference material, the server can draft a complete proposal based on saved examples. Those examples act as references for voice and formatting, allowing the generated document to follow the style of prior winning proposals rather than relying only on generic templates. Bundled examples are also available for users who do not yet have their own proposal library.

The server keeps proposal files in local storage. The supplied tool list includes operations for saving, listing, retrieving, and deleting stored proposals, along with a usage check for the current draft allowance.

How it works

Start with load_examples if you need sample templates, or use save_proposal to add your own successful proposals. list_proposals shows the filenames in the local library, while get_proposal returns the complete text of a selected item. When a new brief is available, call analyze_brief to assess commercial and scope concerns before asking draft_proposal to produce the proposal.

The jabbawocky/proposalcraft MCP server exposes these operations through MCP, so an MCP-compatible client can invoke them as agent tools. The README names Claude Desktop, Claude Code, Cursor, Windsurf, and other MCP-compatible clients as supported environments. Draft generation is subject to the service’s stated monthly usage allowance, which can be checked with usage_status.

Setup and configuration

The README specifies Node.js 18 or newer and provides this launch command:

npx -y github:jabbawocky/proposalcraft

No API key is required. The project description says there is no cloud dependency and that storage is local, so the server is suited to workflows where proposal references should remain on the machine running the MCP process. The provided material does not document additional environment variables or configuration files.

Tools and capabilities

The documented core tools are:

• load_examples: loads bundled proposal templates.
• analyze_brief: reviews budget signals, red flags, scope risks, and go/no-go considerations.
• draft_proposal: creates a full proposal using saved examples as references.
• save_proposal: adds a proposal to the local library.
• list_proposals: lists saved proposals by filename.
• get_proposal: returns the full text of a saved proposal.
• delete_proposal: removes a saved proposal.
• usage_status: reports drafts used and remaining for the month.

The README excerpt also describes related proposal and client-communication workflows, but the core tool list above is the set explicitly supplied for this listing.

Limitations and notes

The free plan is described as allowing five drafts per month. The README also lists a Pro plan at $19 per month with unlimited drafts, so teams should verify current plan terms before relying on the allowance. Only drafting is identified as counting against the limit in the supplied material; analysis and library operations are not marked as draft-consuming.

The server does not replace human review of pricing, scope, timelines, legal language, or client-specific claims. Its output is based on the brief and the examples supplied to its local library. Because no remote storage or API key is required, users must manage backups and access to the local proposal files themselves.