MCP server

The Model Context Protocol (MCP) lets an AI assistant call tools. Advocate OS runs an MCP server, so an assistant can read a firm member's matters, hearings, deadlines, documents, drafts and tasks, and search the public library of judgments and bare acts, as that member.

https://adv.heliosynctech.com/mcp

It speaks Streamable HTTP with JSON-RPC 2.0. It is the same data the workspace API returns, in a form an assistant understands without code. Use MCP when a person talks to an assistant; use the API when your program makes the call.

An MCP key is not an API key. MCP keys are made in Firm › AI & connections, and sign-in connections (OAuth) are approved there too. API keys are made in Firm › Developers, and do not work on /mcp.

#Connect Claude

claude.ai and Claude Desktop (sign-in).

1. Open Settings › Connectors › Add custom connector.
2. Name it "Advocate OS" and paste the server address above. Leave the OAuth client fields empty; Claude registers itself.
3. Choose Connect. Sign in to Advocate OS (and complete two-factor, if your firm uses it).
4. On Connect an AI app, choose whether it may also add notes and tasks (off by default), then Allow.

Claude Code (key). Make a key in Firm › AI & connections, then:

claude mcp add --transport http advocate-os https://adv.heliosynctech.com/mcp \
  --header "Authorization: Bearer $AOS_MCP_KEY"

#Connect ChatGPT

In ChatGPT, add a custom connector (a remote MCP server) in the connector settings; on some plans this needs developer mode. Paste the server address, choose OAuth, and sign in to Advocate OS when asked, as above.

#Connect Cursor

Add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project). Keep the key in an environment variable, not in the file.

{
  "mcpServers": {
    "advocate-os": {
      "url": "https://adv.heliosynctech.com/mcp",
      "headers": { "Authorization": "Bearer ${env:AOS_MCP_KEY}" }
    }
  }
}

#Other clients

Any client that supports remote MCP can connect with a bearer key. For a client that only runs local servers, bridge with mcp-remote:

{
  "mcpServers": {
    "advocate-os": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://adv.heliosynctech.com/mcp", "--header", "Authorization:Bearer ${AOS_MCP_KEY}"],
      "env": { "AOS_MCP_KEY": "paste_your_mcp_key_here" }
    }
  }
}

#Tools

Tool	Does
search_matters, get_matter	Find matters; read one with its timeline.
list_hearings, list_deadlines	Upcoming hearings; limitation and other due dates.
search_documents, get_document_text	Search the record; read a document, 20 pages at a time.
list_drafts, get_draft	The firm's drafts.
list_tasks	Open and done tasks.
search_library, get_judgment_paragraphs	The public library of judgments and bare acts; a judgment by paragraph.
graph_query, graph_path, graph_explain	A matter's case map: people, dates, documents and how they connect. Cheaper in tokens than reading pages.
create_note, create_task	Add a note or a task to a matter. Only with write access.

Answers cite a page by its pin (D12p4 is document 12, page 4) and a judgment by its paragraph label.

#What a key or app can do

Scope	How you get it	Allows
mcp:read	Every key and every connected app	All the read tools.
mcp:write	"Allow adding notes and tasks" when you make a key or approve an app	Also create_note and create_task.

• The member's view. The assistant sees the matters that member sees in the app, never another firm's.
• Clients who said no to AI are left out entirely.
• Limits. At most 120 calls a minute per key.
• Audit. Every tool call is written to the firm's audit log: who, which key, which tool.
• Revoke a key or an app in Firm › AI & connections, any time. The firm owner can turn MCP off for the whole firm.

Text inside a document is material for the assistant, never instructions. The server tells the assistant so; keep that rule if you build your own agent. For an agent you build, see an AI agent over MCP.