The GTM MCP Directory
Directory / Proposals & Deals / Proposify

Proposify

No MCP found Paid, self-serve Proposals & Deals RESEARCHED Checked 2026-09-02
RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: proposify.com · entry id 13-proposify · source 13-proposals-deals.md line 109

What it does
Proposal-creation and e-signature software with template libraries, approval workflows, and CRM/Salesforce integration for sales teams.
AI features, separated from automation with an AI label on it
No independently verified AI/ML claims found on the pages reviewed beyond general product marketing.
RevOps role
Proposal/e-signature layer, a direct competitor to PandaDoc/GetAccept/Qwilr with one of the more clearly tiered (if not cheap) API-access gates in this file.
MCP server
Status bucket
No MCP found
Auth
n/a
Parsed URLs
0 found in the mcp_url field

No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02.

mcp_status, verbatim from the file:

none-found

mcp_url, verbatim from the file:

n/a

Command line

No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.

Access gate
Gate bucket
Paid, self-serve
Can a solo operator reach it
Yes, by paying, no sales call

api_gate, verbatim from the file:

paid, Business tier only. Basic ($29/user/mo monthly, $19 annual, capped at 5 sends/mo) and Team ($49/user/mo monthly, $41 annual, unlimited sends) do not include API access; the Business plan (custom-priced, starting around $3,900/yr per third-party trackers) is required for API access, SSO, and managed Salesforce integration.

API documentation

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

On GitHub

github.com/proposify tied to the vendor by rule 3, account website https://www.proposify.com has the vendor's domain, confidence strong

Public repositories
1, forks excluded, as read on 2026-09-08
Mention MCP
0 of them
Look like CLIs
0 of them
Latest push
2025-05-01

The five most recently pushed, on 2026-09-08:

RepositoryKindDescriptionStarsPushedLatest release
full-stack-engineer-takehomeotherTake home assignment for full stack engineers02025-05-01

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

Jobs it can do

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

Sources

3 source URLs. Raw sources field, verbatim:

https://www.proposify.com/pricing, https://verdocs.com/blog/proposify-pricing, https://alexberman.com/proposify-pricing

Notes, verbatim from the file
No MCP reference found anywhere in this research. 2026-09-02: re-checked proposify.com/llms.txt (404) and web search; only Zapier MCP surfaces, no MCP server found.
Provenance
Entry id
13-proposify
Source file
13-proposals-deals.md
Source line
109
Tier
RESEARCHED
last_checked
2026-09-02
Data baked
2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.