MCP Server (Claude & ChatGPT)

AirSign exposes a remote MCP server (Model Context Protocol) so AI assistants can work with your AirSign account in a conversation: draft an agreement from scratch, create a session, hand you a link to review it in AirSign, and send it to the signers once you approve. It works with Claude (custom connectors) and ChatGPT (developer-mode connectors), and any other MCP-compatible client.

Server URL

https://api.airsign.com.au/mcp

Connecting

Claude

Open Settings > Connectors > Add custom connector (available on Pro, Max, Team and Enterprise plans, and in Claude Code / Desktop).
Enter the server URL above and click Add.
Claude redirects you to AirSign to sign in and approve access for your organisation. That's it - ask Claude to "create an NDA in AirSign" to try it.

ChatGPT

Enable developer mode (Settings > Connectors > Advanced) - required for connectors with write actions.
Add a connector with the server URL above; authentication is OAuth.
Sign in to AirSign and approve access. ChatGPT asks for confirmation before each write action.

Authentication uses OAuth 2.1 with dynamic client registration - no API keys to copy. Access is scoped to the organisation you approve on the consent screen and can be revoked any time from your AirSign settings. API access requires a paid plan.

Built-in Review Step

Documents an assistant creates are drafts by default. The assistant receives a draftUrl that opens the draft in the AirSign editor, so you verify (and tweak) the document before anything is emailed. Only when you approve does the assistant call send_session - or you send it yourself from the editor. Assistants can send immediately, but only when you explicitly ask them to skip review.

Available Tools

Tool	Description
`create_session`	Create a signing session from scratch in the block document format - drafted for review, or sent immediately
`create_template`	Create a reusable template with `{{{variables}}}` for the values that change each time
`create_session_from_template`	Start a session from an active template, filling variables and recipients
`upload_document`	Upload a PDF (max 7MB) to attach to sessions as reference material
`send_session`	Send a reviewed draft - emails the signing invitations
`send_invitation`	Resend an invitation on an already-sent session
`list_sessions` / `get_session`	Check signing progress, find drafts, see who has signed
`list_templates` / `get_template`	Browse templates and their variables/recipients
`get_account_info`	Confirm the connection and the connected organisation

Scopes and Limits

Read tools require a read:sessions / read:templates scope; write tools require the matching write:* scope. Scopes are granted on the consent screen.
Sessions created through MCP count toward your plan's session quota, and plan features (like session expiry settings) are enforced the same as in the app.
Rate limit: 600 MCP requests per hour per organisation.

Example Conversation

You: Draft a simple consulting agreement between us and Jane Smith
     (jane@example.com), and get it ready to sign.

Assistant: I've created "Consulting Agreement - Jane Smith" as a draft
     in AirSign with signature blocks for both parties.
     Review it here before sending: https://app.airsign.com.au/...

You: Looks good - send it.

Assistant: Sent! Jane and your signatory have received their signing
     invitations. I'll check the status whenever you ask.