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. If you ask for changes, the assistant revises the same draft with update_session and the link stays the same. Only when you approve does the assistant call send_session - or you send it yourself from the editor. The server tells assistants to offer you the choice up front - "create a draft to review first (recommended)" or "send now" - and to treat a request like "send this to Jane" as the goal, not as permission to skip the review. Sending immediately only happens when you pick "send now".

Two Ways to Bring In a Document

Authored: assistants write documents in the block document format - a theme (colours, band header, logo), headings, paragraphs, bullet lists, images, input fields (text, date, number, email, checkbox, radio, dropdown, initials, single or in rows) and a signature block per signer. AirSign lays the pages out and places every field.

Uploaded: a PDF you already have, or one the assistant generated, goes through upload_document. Its own form fields are imported automatically and the upload response says whether a signature field exists; whatever is missing is added with fields, anchored to a caption printed in the PDF ("Parent signature") or by page coordinates. The two can be mixed in one session or template, and either way the assistant is told that every signer needs a signature field - the server returns warnings when one is missing.

Available Tools

Tool	Description
`create_session`	Author a signing session from scratch in the block document format (theme, text, input fields, images, signature blocks) - drafted for review, or sent immediately once you choose "send now"
`create_template`	Create a reusable template - authored block documents and/or uploaded PDFs with fields, plus `{{{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); the response lists its pages and form fields so the assistant knows what to import and what to add
`upload_image`	Upload a PNG / JPEG / WebP / GIF (max 2MB) for a document's logo or inline image blocks
`update_session`	Revise a draft after review - rename it, adjust expiry/reminders, fix recipient details, or replace the documents; the draft link stays the same. Sent sessions cannot be changed
`send_session`	Send a reviewed draft - emails the signing invitations
`send_invitation`	Resend an invitation on an already-sent session
`delete_session`	Archive a session (restorable) or delete it permanently. Always asks first: the server refuses to delete until the assistant has shown you the session and you have explicitly confirmed in the conversation - even if the tool is set to "always allow"
`list_sessions` / `get_session`	Check signing progress, find drafts, see who has signed
`get_completed_documents`	Short-lived download URLs for the signed PDFs of a completed session
`list_templates` / `get_template`	Browse templates and their variables/recipients
`get_account_info`	Confirm the connection and the connected organisation

Beyond Signing: App Tools

The same connection reaches the rest of the AirSign suite, so an assistant can work across your whole workspace - add a customer, check what documents they are missing, send them an induction form, and book the job in one conversation.

App	Tools
CRM	`list_customers`, `get_customer` (with document compliance), `create_customer`, `list_customer_types`
Staff	`list_staff`, `get_staff_member`, `create_staff_member`, `list_staff_roles`
Assets	`list_assets`, `get_asset`, `create_asset`, `list_asset_classes`
Compliance	`get_compliance_overview`, `list_document_records`, `get_document_record`, `create_manual_document_record`, `list_requirements`
Training	`list_training_modules`, `create_training_module`, `send_training`
Forms	`list_form_templates`, `get_form_template`, `create_form_template`, `send_form`, `list_form_submissions`
Schedule	`list_schedule_events`, `create_schedule_event` (reports double-booking conflicts)
Timesheets	`list_timesheet_entries`, `create_timesheet_entry`, `review_timesheet_entry`
Social	`list_social_channels`, `list_social_posts`, `get_social_post`, `upload_social_media`, `create_social_post`, `update_social_post`, `delete_social_post`, `publish_social_post`

The same review-first philosophy applies: social posts are composed as drafts or scheduled for your approval unless you explicitly ask to publish, and forms/training are sent through the same tokenised links the apps use.

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
     ([email protected]), 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.