Proposal.Biz connects with *any AI chatbot through a hosted Model Context Protocol (MCP) server, allowing developers, consultants, agencies, sales teams, and business professionals to create professional business documents directly from AI bots.
With the Proposal.Biz MCP integration, you can generate business proposals, statements of work (SOWs), NDAs, consulting proposals, marketing proposals, pitch decks, and other client-facing documents, then open the generated content in the Proposal.Biz b
Scored across 7 tools
Each tool targets a distinct action (check vs. set website, create vs. list documents, session bootstrap, profile read). The clearest boundary — check_website (read-only status check) vs. set_website (only on explicit user input) — is spelled out repeatedly. Minor blur comes from heavily cross-referenced, conditional descriptions where create_proposal partially overlaps with the website card flow, and get_card_state is a tool the agent must never call.
All seven tools use a consistent snake_case verb_noun pattern: check_website, set_website, create_proposal, list_documents, get_profile, get_card_state, initialize_chat. No camelCase or bare-noun outliers, and the verb choice (check/get/list/create/set/initialize) accurately signals read vs. write vs. bootstrap.
Seven tools is well-scoped for a proposal-authoring connector, with no redundant variants. Slightly reduced by get_card_state, which is an internal UI-state tool the agent is explicitly told never to call, leaving six effective tools for the agent.
The surface covers session init, profile read, website setup, document creation, and listing. However there is no get_document (body retrieval), update_document, or delete_document — an agent cannot revise or inspect an existing proposal through the MCP surface and must hand off to the external builder edit URL returned by list_documents.
Check whether the workspace has the user's own website. Call after initialize_chat, before drafting each new document. Continue with the document for every status. If status is missing, do not ask for the website in chat and do not call set_website: when you call create_proposal, its card lets the user add their website or skip, and the card creates the document.
Inputs: no named parameters. Returns: status, message, pageLimit
Create a new proposal from plain Markdown content. Provide the approved content as standard Markdown text (headings, paragraphs, lists, tables) and a short brief; the platform designs the pages, layout, images, and charts. Do not send JSON, HTML, page markers, or pre-structured page objects. Call check_website before drafting, after initialize_chat has been called in this conversation. If the workspace still has no website, the result shows a card where the user can add one or skip; the card then creates the document. If the user shares their own website in chat, pass it as websiteUrl. If the user asked for specific colors, fonts, or a look for this document, pass them as theme; otherwise omit it and the workspace theme is used.
Inputs: brief (required), title (required), markdown (required), theme, +6 more. Returns: url, theme, title, status, +2 more
Used only by the Proposal.biz card to restore its state after a chat reload. Never call this yourself.
Inputs: cardId (required). Returns: url, title, status, proposalId, +2 more
Get the connected Proposal.Biz profile: a stable account id, display name, email, and workspace name
Inputs: no named parameters. Returns: id, name, email, nickname
Initialize this Proposal.biz chat from the user's first message. Call exactly once at the start of a new conversation, before other tools. Do not call again in this chat, and do not call when starting another document in the same chat. Pass a short paraphrase of the first ask, with no names, emails, or URLs.
Inputs: summary (required). Returns: status
List documents in the connected workspace that this user can open. Owners see every non-deleted document, including those in folders. Members see documents they created or collaborate on. Returns id, title, status, render type, last updated time, and a builder edit URL. Optional title search, status, and render type filters. Does not return document body.
Inputs: limit, query, offset, status, +1 more. Returns: limit, total, offset, hasMore, +1 more
Save the user's own website for the workspace. Call this only when the user types their website in chat (pass websiteUrl) or declines it in chat (pass skip: true); never call it just to check, use check_website for that. If status is missing, a card asks the user for their website (logo, colors, company details, and reusable service descriptions come from it) with a Skip option; let the card speak for itself and wait without sending a separate chat reply. If the user says they added or skipped it in the card, it is already saved: do not call this again. Proceed with the document after status is has_website, started, skipped, or not_needed. Use the user's own site, never a client's site.
Inputs: skip, cardId, websiteUrl. Returns: status, message
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
