AI assistant connectors

Name: SignAndGo
Author: SignAndGo

Connect claude.ai, ChatGPT, or any MCP-compatible AI assistant to your SignAndGo workspace. Two layers of consent gate every request: token scope (read or write) granted at connect time, and a per-envelope flag you control on each envelope.

Two ways to connect

Through MyAndGo Platform

Recommended. Connect once at myandgo.com.au/mcp and the AI gains access to every AndGo product you've subscribed to (SignAndGo, ShareAndGo, etc.). Single OAuth flow, federated tokens issued per request.

Tools appear under the signandgo. namespace.

Direct connection

For SignAndGo-only access. The AI client discovers SignAndGo via OAuth 2.1 metadata at/.well-known/oauth-protected-resource, registers itself via DCR (RFC 7591), then runs the standard authorization-code + PKCE flow.

Tools appear under the root namespace.

Supported clients

The SignAndGo connector works through the open Model Context Protocol (MCP), so any MCP-capable AI client can connect. What works well depends on the client's runtime environment. Sandboxed web clients (like claude.ai web) have networking constraints that affect file uploads but not search, read, or small writes.

Client	Read & search	Small writes	File uploads
claude.ai web	✓ Full speed	✓ Status, void, resend, send-from-template	⚠ Slow / unreliable for files >~20KB
Claude Desktop	✓	✓	✓ Recommended for uploads
ChatGPT (when MCP ships)	✓	✓	✓ Expected to work end-to-end
Custom MCP clients	✓	✓	✓ Full control over upload path

claude.ai web's sandbox blocks outbound HTTPS to storage hosts, so file bytes have to flow through the LLM's tool-call output channel, which is slow for documents larger than about 20 KB. If you primarily need to send new files for signing from Claude, use Claude Desktop. If you primarily need to manage existing envelopes (status, reminders, voids, sending from existing templates), claude.ai web is fully capable.

Setting up claude.ai

Open claude.ai → Settings → Connectors → Add connector.
Paste the connector URL: https://signandgo-backend-308289583348.australia-southeast1.run.app/api/mcp/v1
claude.ai discovers the OAuth endpoints automatically and walks you through the authorize flow.
Sign into SignAndGo when prompted, then choose which scopes to grant (Read / Write).
You can now ask Claude things like "List my draft envelopes" or "Void envelope titled 'May invoice'".

Available tools

list_envelopesread

List envelopes accessible to the AI

get_envelope_statusread

Status + recipient progress for one envelope

download_signed_pdfread

Download URL for a completed envelope

list_recipientsread

List recipients on one envelope

create_envelopewrite

Create a draft envelope from a document + recipients

send_for_signingwrite

Send a draft envelope to its signers

void_envelopewrite

Void an in-flight envelope

resend_to_recipientwrite

Resend signing request to one recipient

Per-envelope consent

By default, no envelopes are visible to AI integrations, even with a read-scope token. Enable AI access per envelope via the AI assistant access panel on the envelope detail page, or set a workspace-wide default in workspace settings.

Two-layer consent

Token scope (read or write), granted at OAuth connect time
Per-envelope flag (ai_access / ai_write_access), set on each envelope individually

A tool call succeeds only when both checks pass.

Audit + revoke

Every AI tool call is logged in Audit Trailwith the tool name, integration, success/failure, and which envelopes it touched.

Revoke any active integration anytime from Settings → AI Assistants. Federation tokens auto-expire after 5 minutes.