Connect Claude, ChatGPT, Cursor, VS Code and other AI assistants to your Rilin workspace. Your assistant can find agreements, draft and review contracts with Rilin’s legal processes, follow negotiations, and move documents through approval and signing. It always acts as you, with your Rilin permissions.

Setup

General

The Rilin MCP server uses Streamable HTTP and is available at:

https://mcp.rilin.ai/mcp

Sign-in uses OAuth. The first time your assistant connects, a browser window opens on Rilin’s sign-in page. Sign in, choose your organisation and permissions, then approve.

You need a Rilin account that belongs to an organisation. The connector does not create accounts. Ask your Rilin administrator for an invitation if you do not have one.

Claude

Open Settings > Connectors and select Add custom connector.
Enter Rilin as the name and https://mcp.rilin.ai/mcp as the URL.
Select Connect, sign in to Rilin and approve access.
In a conversation, open the tools menu and turn on Rilin.

On Team and Enterprise plans, an owner may need to add the connector for the organisation before members can connect.

Claude Code

claude mcp add --transport http rilin https://mcp.rilin.ai/mcp

Then run /mcp in Claude Code and select Authenticate for rilin.

ChatGPT

Open Settings > Apps & Connectors. Depending on your plan, custom connectors may need developer mode.
Create a connector with the URL https://mcp.rilin.ai/mcp and OAuth authentication.
Sign in to Rilin and approve access.

Cursor

Install in Cursor

To set it up manually, add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "rilin": {
      "url": "https://mcp.rilin.ai/mcp"
    }
  }
}

VS Code

Install in VS Code

To set it up manually, add this to .vscode/mcp.json in your workspace:

{
  "servers": {
    "rilin": {
      "type": "http",
      "url": "https://mcp.rilin.ai/mcp"
    }
  }
}

Other clients

Follow your client’s instructions for remote MCP servers and use https://mcp.rilin.ai/mcp as the server URL. The server supports the MCP authorization specification: OAuth 2.1 with PKCE, Dynamic Client Registration and client ID metadata documents. No client secret or API key is needed.

If your organisation manages your device or network, your IT team may need to allow mcp.rilin.ai.

Permissions

Rilin’s consent screen names the application asking for access and lets you choose what to grant.

Permission	Allows your assistant to
Read	Read legal workspace information and documents you can access.
Write	Run Rilin AI processes and take permitted legal actions, including sharing and sending for signature.
Admin	Manage templates, workflow definitions and legal position playbooks, within your permissions.

Your assistant can never do more than you can in the Rilin app. Tools that need a permission you did not grant are hidden.

If Rilin does not recognise the application, the consent screen shows an Unverified application warning and leaves Admin unticked. Only approve applications you set up yourself.

Common use cases

Stay on top of your queue: “What agreements are waiting on me this week?”
Draft from your templates: “Draft an NDA with Acme Pvt Ltd from our standard template.”
Review a counterparty’s changes: “Summarise the latest changes to the reseller agreement and flag anything risky.”
Decide tracked changes: “Accept the formatting changes and reject the change to the liability cap.”
Get approvals: “Send the MSA to finance for internal approval.”
Chase signatures: “Who still has to sign the lease, and when was the last reminder sent?”
Track obligations: “List the obligations in the signed services agreement.”

Tools

The server groups its tools by area. Your assistant sees only the tools your permissions and your organisation’s features allow. See the tool reference for every tool.

Area	What your assistant can do
Work queue and agreements	Find what is waiting on you. Look up agreements, participants, versions, risks and obligations.
Drafting and templates	Start drafts from templates or a conversation, follow progress, manage templates.
Documents and tracked changes	Read documents, comment, accept or reject tracked changes, ask Rilin about a document.
Contract requests	Raise, route, accept or reject requests for new contracts.
Negotiation and sharing	Follow negotiation turns, share drafts, notify the counterparty.
Internal review	Request approvals and record approvals or objections.
Workflow playbooks	Run your organisation's workflow playbooks and supply their inputs.
Signing and stamping	Start and track e-signature, send reminders, calculate stamp duty, record e-stamps.
Position Playbooks	Build and apply negotiation positions. Available when enabled for your organisation.
Title Checks	Run property title checks and manage findings. Available when enabled for your organisation.

Every tool declares whether it only reads, changes existing data, or reaches people outside Rilin, such as a counterparty or signer. Keep your assistant’s confirmation prompts turned on for tools that write. Take care when using Rilin alongside other MCP servers, to limit the risk of prompt injection.

How it works

Rilin does the legal work. Drafting, redlining, review and Ask Rilin run inside Rilin. Your assistant starts them and relays the results, including any questions Rilin needs you to answer.
Long tasks run in the background. A drafting or review request returns straight away, and your assistant checks progress until it finishes.
Retries are safe. Tools that change data accept an idempotency key, so a retried request is not carried out twice.
Some steps finish in Rilin. Uploading files, editing in the document editor, signing and paying stamp duty happen in the Rilin app. Your assistant gives you a link to continue there. Files are never sent through your assistant.

Manage access

To see or revoke the assistants connected to your account:

In Rilin, open Settings > Security.
Open Connected AI assistants.
Select Revoke next to the connection.

Revoking takes effect immediately. You can also remove the connector from your assistant’s settings.

Security and privacy

Every request runs as the signed-in user, in the organisation chosen when connecting, with that user’s role-based permissions.
Sign-in always happens on Rilin’s own page. You never give your password or an API key to your assistant.
Access tokens are short-lived and renewed automatically. Each connection has a fixed lifetime, after which you sign in again.
The server instructs assistants to treat document text as data, never as instructions, to help protect against prompt injection hidden in contracts.
Rilin keeps a record of every action taken through the connector.
Rilin stores and processes your data in India. Your AI assistant’s provider processes what your assistant reads under that provider’s own terms.

Read the Rilin privacy policy.

FAQ

The sign-in window did not open.

Allow pop-ups for your assistant, or reconnect from its settings.

I see “Unverified application” on the consent screen.

You are connecting a client Rilin does not recognise. Continue only if you set it up yourself.

A tool I expect is missing.

You may not have granted the permission it needs, or your organisation may not have that feature. Ask your assistant to run get_connection_context. It shows your organisation, permissions and available features.

My assistant says a draft or contract was not found.

Drafts and agreements are identified by a workflow_id and signed contracts by a contract_id. Check that your assistant used the right one and that you can open the item in Rilin.

My assistant says a job is still running.

Drafting and review take time. Ask your assistant to check again in a minute.

I got a “too many requests” error.

Requests are rate limited to protect the service. Wait a moment and try again.

I am asked to sign in again.

Your connection reached the end of its lifetime or was revoked. Reconnect from your assistant.

Support

Contact your Rilin account team. Include your assistant’s name and when the problem happened. Never send tokens, passwords or document contents.