Legalesign MCP server
Yes. Legalesign publishes an official MCP server at https://mcp.legalesign.com/mcp. It's hosted. It offers 19 tools. We last checked it on 22 Nov 2026.
Official: answers MCP requests at mcp.legalesign.com, on Legalesign's own domain legalesign.com. Checked 22 Nov 2026. Maintained by Stuart Brameld.
Key facts
As of 22 Nov 2026, Legalesign's official MCP server scores 55/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 54 of our 55 checks in the last 90 days and lists 19 tools.
How the Agent Readiness Index works · Wrong? Suggest a correction
Legalesign MCP server review
55/100
Legalesign's MCP server scores 55/100 on MartechDB's Agent Readiness Index: usable by AI agents, with gaps.
The good
Hosted by Legalesign: connect by URL, with nothing to install
The bad
Nothing we've found.
Not checked yet: how you sign in; a docs page listing its tools; what agent access costs. Anything not checked scores nothing.
Official MCP server
Legalesign MCP server
- Address
- https://mcp.legalesign.com/mcp
- Runs
- Hosted
- Sign-in
- Official MCP Registry
- Not listed
- How we know it's official
-
- Answers MCP requests at mcp.legalesign.com, on Legalesign's own domain legalesign.com.
- Tools
- 19 tools · listed 22 Nov 2026
- First seen
- 1 Oct 2026
- Last checked
-
Reachable ·
16 Nov 2026: reachable17 Nov 2026: reachable18 Nov 2026: reachable19 Nov 2026: reachable20 Nov 2026: reachable21 Nov 2026: reachable22 Nov 2026: reachable
- Uptime
- 98.2% · 54 of 55 checks reachable since 1 Oct 2026
Legalesign MCP server tools (19)
As the server lists them. Names and descriptions are the vendor's own.
-
lookupLook up a Legalesign API entity by name. Covers: GraphQL schema entities (type, enum, input, query, mutation), REST API endpoints (e.g. "get document", "post document", "get signer component token"), and Signer component events (signingSuccess, signingFail, fieldChange, FailureReason). Use the `api` parameter to restrict to a specific API when you know which one you are working with.
-
searchSearch across all Legalesign documentation. Specify product_area to scope results. Returns matching page summaries — use 'lookup' for specific schema entities, REST endpoints, or component events; use 'getGuide' to fetch full guide content. When results relate to bulk send, always ask the user whether they want a ready-made CSV template file to populate with their data, or whether they already have their own file to upload.
-
getGuideGet a Legalesign how-to guide, explanation, or example page. Use for conceptual questions or task-oriented guides. Specify product_area to scope results. When the topic relates to bulk send, always ask the user whether they want a ready-made CSV template file to populate with their data, or whether they already have their own file to upload — the template is available to download directly from the Bulk Send page in the app.
-
listGuidesList available guide pages, optionally filtered by product area. Use this to discover valid topic strings before calling getGuide.
-
listGroupsList the groups the authenticated user belongs to. Returns each group name and its groupId. Always use the groupId value (never the group name) when calling other tools.
-
listReportsList the reports that have been requested for a group, newest first, with their status, level, format and period. Completed reports include a link to the report file, which holds the data. Check this first: an existing COMPLETED report that covers the right period and level can be reused instead of requesting a new one. Reports expire, so an old one may be gone.
-
getReportGet a single report by its ID, including its status and (when complete) a download link. Reports are generated in the background, so poll this after requestReport until the status is COMPLETED or FAILED, waiting a few seconds between checks. The result includes a link to the report file, and the file is the only place the report data is. To answer a question about the user's documents, open that link and read the file (JSONL has one record per line). If you cannot open links, give the link to the user and say so; do not guess at the contents. If the result warns that the report is large, tell the user before reading it and offer a narrower period or level instead of loading the whole file. Very large reports can be split across several files, and the link covers the first one.
-
requestReportRequest a report of the documents sent from a group. Use this to answer questions about the user's documents: what was sent, to whom, and the status of each one. The report is generated in the background and starts as PENDING, so follow up with getReport until it is COMPLETED. Defaults: unless the user says otherwise, request the last whole calendar month (omit start and end and the server uses it), at the DOCUMENT level, in JSONL. Say those assumptions in one sentence, then request the report, and let the user change the period, level or format. Only ask a question if the group is unclear (the user belongs to several) or the period is vague, such as "recently". Levels: DOCUMENT is one row per document (counts, statuses, who sent what); RECIPIENT is one row per recipient (who has signed, who has not, email problems), so pick it when the question is about people; FIELD is one row per recipient including the values of every non-admin field, which is much larger, so use it only when the…
-
deleteReportPermanently delete a report and its generated file. This cannot be undone. Only call this after the user has explicitly confirmed which report to delete.
-
listTemplatesList available templates for a group. Use this to discover templateId values before calling getTemplate or previewSend.
-
getTemplateGet full details of a template including its roles and expected number of recipients. Use this to confirm the correct template before sending.
-
previewSendPreview a document send before executing it. Always ask the user for recipient first name, last name, email, and a document title before calling this tool — do not default to the template name without asking. Always call this before confirmSend — show the returned summary to the user and ask for explicit confirmation. Only include senderFields if getTemplate showed sender fields on the template.
-
confirmSendExecute a document send. Only call this after previewSend and the user has explicitly confirmed they want to proceed. Only include senderFields if getTemplate showed sender fields on the template. The title must have been provided or confirmed by the user — do not silently default to the template name.
-
previewBulkSendPreview a bulk send before executing it. Before calling this tool you must: (1) parse the uploaded file into rows, (2) call getTemplate to get roles and sender fields, (3) propose a column mapping and ask the user to confirm it, (4) ask the user for a reference name for this bulk send, (5) ask the user for a default document title to use for all documents — or ask if there is a title column in the file to use instead, (6) call listSchedules and ask the user if they want a reminder schedule applied — if yes, include the chosen scheduleId in columnMapping. Shows a sample of the first 3 documents, total count, and checks available credits. Always call this before confirmBulkSend.
-
confirmBulkSendExecute a bulk send. Only call this after previewBulkSend and the user has explicitly confirmed they want to proceed.
-
getBulkSendStatusGet the overall status and progress of a bulk send by its batch ID.
-
getBulkSendDocumentsGet per-document details for a bulk send, including recipient status.
-
listSchedulesList available reminder schedules for a group. Use this to let the user pick a schedule to apply to recipients in a send or bulk send.
-
getBulkSendCsvTemplateGenerate a CSV template with the correct column headers for a bulk send. Use this to give the user a template to fill in before uploading for a bulk send.
Connect your AI to Legalesign
Add the official Legalesign MCP server to Claude, ChatGPT or your editor.
Connect Legalesign MCP to Claude
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it Legalesign, paste the address below and click Add.
Connect Legalesign MCP to ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it Legalesign and paste the address below.
ChatGPT usually only connects to servers with self-serve sign-in or none.
Connect Legalesign MCP to Cursor
Opens Cursor if it's installed. If nothing happens, use the JSON below.
Connect Legalesign MCP to VS Code
Opens VS Code if it's installed. Otherwise add the JSON settings from the Cursor tab to your .vscode/mcp.json.
Legalesign MCP server questions
Does Legalesign have an official MCP server?
Yes. Legalesign publishes its MCP server itself. Its address is on Legalesign's own domain (mcp.legalesign.com). MartechDB only lists servers a vendor publishes, never community copies.
What is the Legalesign MCP server URL?
The address is https://mcp.legalesign.com/mcp.
How do I connect Legalesign MCP to Claude, ChatGPT or Cursor?
In Claude, add https://mcp.legalesign.com/mcp as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http legalesign https://mcp.legalesign.com/mcp
What can the Legalesign MCP server do?
It offers 19 tools, including lookup, search, getGuide, listGuides and listGroups (as listed on 22 Nov 2026).
Is the Legalesign MCP server in the official MCP Registry?
No. Legalesign hasn't published it to the official MCP Registry.
Is the Legalesign MCP server working?
Yes. It answered our most recent check. We last checked it on 22 Nov 2026.
What are the alternatives to Legalesign's MCP server?
In Proposals & e-signature, the most agent-friendly alternatives with an official MCP server are Qwilr (91/100), AutoRFP.ai (91/100), Apropo (89/100), SignEasy (89/100) and PandaDoc (85/100). Legalesign scores 55/100 on the same index.
Alternatives to Legalesign's MCP server
Vendors in Proposals & e-signature with an official MCP server, the most agent-friendly first. Legalesign scores 55/100.
Compare all 20 Proposals & e-signature vendors →Change history
What we've seen change for Legalesign, newest first.
-
Legalesign: Legalesign MCP server: 4 tools added, 1 removed (now 19)
-
Legalesign: Legalesign MCP server: 6 tools added (now 16)
-
Legalesign: Legalesign MCP server: 6 tools added (now 10)
-
Legalesign: Legalesign MCP server: 1 tool added (now 4)
Use with AI
Connect your AI to MartechDB
Then ask it about Legalesign, or any of the 1,850 marketing tools with an official MCP server. Free, no sign-in.
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it MartechDB, paste the address below and click Add. There's no sign-in.
The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.
Claude Code
Run this in your terminal:
ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it MartechDB, paste the address below and choose No authentication.
Developer mode is on Plus and Pro plans, and on Business, Enterprise and Edu if an admin allows it.
API
The same data as JSON, with no sign-in. See the OpenAPI description for every endpoint and field.
CLI
Search the directory and print the command to connect a vendor's server, from your terminal. Needs Node 18 or later. View on npm
Show that your MCP server is verified
If you work at Legalesign, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.
Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.