How to Connect BoldSign to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → BoldSign, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

BoldSign + Meta Muse

BoldSign e-signatures in the US, EU, Canada or Australia region: find documents and see who has signed, download signed PDFs and audit trails, send files or templates for signature, remind, extend, change signers and prefill fields, and browse templates, sender identities, contacts, teams, users, brands and API credits.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

BOLDSIGN_API_URL, BOLDSIGN_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a BoldSign plan that includes the API, or a free Sandbox account.

1. Sign in to BoldSign (https://app.boldsign.com, EU accounts https://app-eu.boldsign.com) and open API in the left menu, then API Key.
2. Click Generate API Key, choose Sandbox (free, watermarked documents, 50 requests an hour) or Live, optionally set a validity date, and copy the key into BOLDSIGN_API_KEY. It is sent in the X-API-KEY header and has every scope.
3. Set BOLDSIGN_API_URL to the API address of your account's region, without a trailing slash: https://api.boldsign.com (US), https://api-eu.boldsign.com (EU), https://api-ca.boldsign.com (Canada) or https://api-au.boldsign.com (Australia). The browser address after sign-in tells you the region: app-eu is EU, app-ca Canada, app-au Australia, plain app US.
4. Install the connector and run boldsign_list_documents to check key and region.

Finding documents and who has signed:

• boldsign_list_documents lists documents you sent or received, newest first, with status, sender, each signer's status, cc, labels and dates. Filter by text, status (WaitingForMe, WaitingForOthers, NeedAttention, Completed, Declined, Revoked, Expired, Draft, Scheduled), transmit_type (Sent, Received, Both), a date range on the sent or expiry date, labels, brands, sender or signer email.
• boldsign_list_team_documents shows the documents of your team (team admins: of the teams they manage), filterable by team and user. boldsign_list_behalf_documents shows documents sent on behalf of others through a sender identity, or sent on your behalf.
• boldsign_get_document reads one document in full: files, each signer with order, status, viewed, authentication and form field values, cc, the event history, expiry, reminder settings and any revoke or decline message.

Signed files: boldsign_download_document returns the signed PDF once the document is completed, otherwise its current state; several files come as one combined PDF or, with format Individually, as a ZIP. boldsign_download_audit_log returns the audit trail PDF with every event (sent, viewed, signed, declined), its time, email and IP address. For documents sent on behalf of someone, pass the sender identity email in on_behalf_of.

Sending for signature:

• From a template: boldsign_list_templates, then boldsign_get_template for the role indexes and field ids, then boldsign_send_from_template with one roles entry per role (roleIndex, signerName, signerEmail, optional existingFormFields to prefill). Roles left out keep the template's default signer; role_removal_indices drops roles from this document.
• A file: boldsign_send_document takes PDF, Word or image files as public URLs in file_urls (BoldSign downloads them) or as Base64 data URIs in files, never both. Each signer has name, emailAddress, optional signerOrder, signerType (Signer, Reviewer or InPersonSigner) and formFields (Signature, Initial, CheckBox, TextBox, DateSigned, RadioButton, Dropdown, Name, Email, each with page and bounds). Instead of placing fields you can use text tags written in the document (use_text_tags) or let BoldSign turn existing form fields and blank lines into fields (auto_detect_fields).
• Both take a title and message, cc, signing order, expiry (Days by default, 60 days; Hours or SpecificDateTime), automatic reminders, a brand, labels and on_behalf_of for a sender identity that is Verified. disable_emails sends no emails; boldsign_get_embedded_sign_link then gives a direct signing link per signer, optionally time-limited and with a redirect address. boldsign_send_draft sends a document saved as draft.
• Sending is asynchronous: the answer carries the documentId at once, and a moment later boldsign_get_document shows whether it went out (a failed send appears in its history).

Sending is real: sending, reminding, changing a signer and creating a sender identity email real people, a Live document is legally binding and may use API credits. The AI shows you the file or template, the signers and the message, and sends only after your clear yes.

Follow-up: boldsign_remind_document reminds all pending signers or only the given emails. boldsign_extend_expiry moves the expiry of a document in progress: a date yyyy-MM-dd for expiry in days, a number of hours for expiry in hours, an ISO 8601 date-time for a specific expiry. boldsign_change_recipient replaces a signer who has not signed yet, with a reason recorded in the audit trail. boldsign_prefill_fields sets field values before the signers fill them (field ids from boldsign_get_document).

Account: sender identities with boldsign_list_sender_identities, boldsign_get_sender_identity and boldsign_create_sender_identity (BoldSign emails the person an approval request; the identity can be used once its status is Verified, statuses are Pending, Verified and Denied). Contacts with boldsign_list_contacts, boldsign_get_contact, boldsign_create_contacts and boldsign_update_contact. Teams, users (role Admin, TeamAdmin or Member, status Active or Invited) and brands are read only. boldsign_get_api_credits shows the credit balance and how many are used.

Switched off at install: boldsign_revoke_document (stops signing and tells the signers why; the document cannot be resumed) and boldsign_delete_document (moves it to the trash, or erases it for good with delete_permanently). Neither can be undone, so a workspace admin turns them on when the team needs them.

Data formats: ids are GUID strings (documentId, templateId). Dates such as createdDate, activityDate and expiryDate are Unix timestamps in seconds; filters take ISO 8601 (2026-10-01T00:00:00Z). Document status is InProgress, Completed, Declined, Expired, Revoked, Draft or Scheduled; signer status NotCompleted, Completed, Declined, Revoked or Expired. Template roles are numbered from 1. Field bounds (x, y, width, height) are measured from the top left of the page, and field ids use letters, digits and underscores only.

Paging: list tools take page (from 1) and page_size (1 to 100, default 10) and return pageDetails with totalRecordsCount and totalPages, plus the items in result (results for teams). Beyond 10,000 documents the AI passes the cursor of the last document as next_cursor.

Limits: 2,000 requests an hour per account on Live and 50 on Sandbox, counted for API key and OAuth together. Sandbox documents carry a watermark. On credit-based plans each document sent through the API uses credits.

Common errors: 401 means a wrong or expired key, or a key used against another region's address. 403 means the plan lacks the API or the user may not see the item. 400 comes with a message for invalid input, for example an unknown role index, a missing signer email or a file BoldSign cannot read. 429 means the hourly limit is reached; wait until X-RateLimit-Reset.

The connector does not create or edit templates, does not manage webhooks, does not create teams, users or brands and does not delete contacts.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the BoldSign tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

Example prompts

• "Which documents are still waiting for others to sign, and who exactly has not signed yet?"
• "Has [email protected] signed the NDA we sent on Monday? Show me the event history."
• "Download the signed PDF and the audit trail of the service agreement with Acme."
• "Send our freelance contract template to [email protected] as the contractor. Show me the roles and the message before sending."
• "Remind the pending signers of the lease agreement and extend its expiry to 30 November."

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Microsoft Copilot