Grok e-signature MCP guide

Send documents for e-signature with Grok

Grok connects to eSign 360 through the xAI API, which supports remote MCP servers. Point the MCP tool at the eSign 360 server and Grok can prepare, send, track and remind documents for signature.

Start free ›

In short

  • What it is: a remote MCP server for legal e-signatures, built into eSign 360 by 360 SaaS Pty Ltd, an Australian company.
  • Server address: https://admin.esign360.ai/mcp
  • Works with: The xAI API (Responses API) with a remote MCP tool. The xAI documentation describes the API route; it does not describe a connector screen in the Grok app, so this guide covers the API.
  • Price: AI assistant access is A$10 a month plus GST on the API plan, charged only while it is on. eSign 360 is free for Portal 360 customers, and the free tier is 5 documents a month.
  • Control: Grok asks before it sends, and every action is in your audit log.

How to connect eSign 360 to Grok

Before you start:

  1. On the eSign 360 API plan, an administrator switches on AI assistant access in Settings. It is A$10 a month plus GST, charged only while it is on.
  2. You sign in with your own eSign 360 account, so the assistant acts as you and your permissions apply.

Then:

  1. Complete the eSign 360 OAuth sign-in with your own client to get an access token. The server publishes its OAuth details at https://admin.esign360.ai/.well-known/oauth-authorization-server, supports PKCE and dynamic client registration, and issues refreshable tokens.
  2. Call the xAI Responses API with a tool of type mcp, the eSign 360 server_url and your access token in authorization.
  3. Limit the tools Grok can see with allowed_tools, for example the read-only tools first.
  4. Ask Grok to prepare a document. Review the signers it returns and confirm before it sends.
curl https://api.x.ai/v1/responses \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $XAI_API_KEY" \
  -d '{
    "model": "YOUR_GROK_MODEL",
    "input": [{"role": "user", "content": "List my documents that are waiting for a signature."}],
    "tools": [{
      "type": "mcp",
      "server_url": "https://admin.esign360.ai/mcp",
      "server_label": "esign360",
      "authorization": "$ESIGN360_ACCESS_TOKEN",
      "allowed_tools": ["list_documents", "get_document"]
    }]
  }'

xAI supports the streaming HTTP and SSE transports, and its Responses API does not currently offer per-call approval, so keep allowed_tools tight and confirm sends in your own application before calling send_document.

What you can ask Grok to do

AskWhat happens
“Send the attached NDA to sam@acme.com.”It prepares the document and shows you the signers. Nothing is emailed until you say yes.
“Which documents are still waiting?”It lists your documents and their status.
“Remind everyone who has not signed.”It sends reminders to the outstanding signers.
“Cancel the lease renewal.”It voids the document.
“Get me the signed copy.”It returns a link to the signed PDF or audit certificate that expires in 10 minutes.

The full list of tools is on the MCP server page. Signatures are legally recognised in Australia, and every signed document carries a tamper-evident certificate of completion. See are electronic signatures legal in Australia.

Questions about Grok and eSign 360

Can I use eSign 360 inside the Grok app?

The xAI documentation covers remote MCP through the API. We do not rely on an app connector for Grok today, so use the xAI API as shown.

How does Grok sign in to eSign 360?

You pass an eSign 360 OAuth access token in the authorization field. The token is issued to you after sign-in, so Grok acts as you and your permissions apply.

Which Grok models work?

Any xAI model that supports tools in the Responses API. Check the xAI documentation for the current model names.

Connect other assistants

Source for the Grok steps: xAI documentation: remote MCP tools. Menus and labels can change, so check the vendor’s documentation if a step looks different.