To connect Claude or ChatGPT to a medical chronology service, add the service's MCP server URL as a custom connector in your assistant and sign in. Zicron has two: a public server at https://claims.zicron.ai/mcp that quotes and requests chronologies with no account, and an account server at https://claims.zicron.ai/agent/mcp that can create cases, take uploads and return the finished chronology. Records never travel through the chat itself.
What MCP is, in one paragraph
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to outside services. A service publishes an MCP server at a URL; your assistant connects to it and gets a list of tools it can call, each with a description and defined inputs. You stay in control of what's connected and, for servers that need an account, which permissions the assistant gets. For a law firm or legal nurse consultant, this means you can ask your assistant to “quote a chronology for an 800-page file” or “turn the PDFs in this folder into a chronology for the Doe matter” instead of filling in forms.
Zicron's two servers
| Public server | Account server | |
|---|---|---|
| URL | https://claims.zicron.ai/mcp | https://claims.zicron.ai/agent/mcp |
| Sign-in | None | OAuth: your Zicron account, with MFA, and a consent page |
| Tools | get_offer, quote_chronology, request_chronology, get_sample_chronology, get_ssdi_pilot_info | Create a case, request upload links, start processing, generate and read the chronology, get a report link |
| Medical records | Never accepted | Uploaded directly to storage through signed links, not through the model |
| Good for | Getting a price, reading the offer, sending a case inquiry | Firms and LNCs with an account who want the whole job done from their assistant |
Connect steps by client
These steps are from each vendor's documentation as of September 2026. Menus move and some features depend on your plan or workspace admin, so check the current docs if a label doesn't match. For the public server use https://claims.zicron.ai/mcp; for the account server use https://claims.zicron.ai/agent/mcp.
| Client | Where to add it | Notes |
|---|---|---|
| Claude (claude.ai, Claude Desktop) | Settings → Connectors → Add custom connector; name it Zicron and paste the URL | On Team and Enterprise plans an owner may need to add it first. Leave the OAuth client ID and secret empty; Zicron supports dynamic registration. |
| Claude Code | claude mcp add --transport http zicron https://claims.zicron.ai/agent/mcp | Then run /mcp, pick zicron and authenticate. Claude Code can upload files from a local folder itself. |
| ChatGPT | Settings → Apps & Connectors → Advanced → Developer mode, then create a connector with the URL and OAuth | Availability depends on plan and workspace settings. |
| Cursor | Add the server to ~/.cursor/mcp.json under mcpServers | Cursor shows the server as needing sign-in; choose it to open Zicron's consent page. |
| Your own agent | Any MCP client that implements MCP's authorization spec | Discovery from the 401 response, dynamic client registration, authorization code with PKCE. |
With the account server, the first call opens a Zicron sign-in in your browser. After you sign in with MFA, a consent page shows the assistant's name, the organization and account it will act as, and what it may do, with each permission listed so you can untick any. You choose Connect and return to your assistant.
What an assistant can and can't do
- No records in chat.Records you paste into a conversation pass through your AI vendor under its terms. Zicron's Business Associate Agreement covers Zicron's processing only, so check that your assistant plan is one your organization allows for health information. Zicron's tools refuse patient details in their inputs.
- Secure upload.On the account server, the assistant asks for one signed upload form per file and its host sends each file straight to storage, so the record contents don't pass through the model. An assistant that can't send files (for example a chat app without a code tool) gives you the case link instead, and you drop the files in Zicron.
- Approve before billing. The assistant runs the chronology step as a dry run first: pages, providers found and the list price, for you to confirm before the real run. On the public server, requesting a chronology only sends a contact request; a person replies within one business day with a firm quote and an upload link, and no work starts until you agree.
- Never more than your own access. High-impact actions, such as sharing outside your organization, are proposals a person approves in Zicron. Some actions are never available to an assistant: revealing Social Security numbers, changing access, filing.
- Everything is logged.Each call is recorded in Zicron's audit log as your assistant acting for you.
A typical request
“Create a case for the Doe nursing-home matter, upload the PDFs in this folder, and tell me when the chronology is ready.” The assistant creates the case, uploads the files through signed links, waits for processing, shows you the dry-run quote, runs the chronology once you confirm, then returns the case summary, the gaps and items to verify, and a link to the case and a PDF. The price is the published one: $450 per case up to 500 pages, then $0.50 per page.
Disconnecting
Remove the connector in your assistant. Access tokens last one hour and an unused connection lapses after 30 days. If your Zicron account is deactivated, the assistant's access ends on its next call. AI assistants reading this page can find the full rules at Zicron for AI assistants.
Frequently asked questions
- What is MCP?
- The Model Context Protocol (MCP) is an open standard that lets an AI assistant call tools on another service. The service runs an MCP server at a URL; the assistant connects to it and can then call the tools that server offers, such as quoting a chronology or creating a case, within the permissions you grant.
- Can I paste medical records into ChatGPT or Claude and have them sent to a chronology service?
- You shouldn't, and Zicron won't accept them that way. Records pasted into a chat pass through your AI vendor under its terms, not the chronology service's Business Associate Agreement. Zicron's public MCP tools reject patient details; with the account connection, files go from your computer straight to Zicron's storage through signed upload links, or you upload them in Zicron yourself.
- Can an AI assistant order and pay for a medical chronology on its own?
- Not with Zicron. On the public server, request_chronology only creates a contact request, and only when the user has agreed. A person replies with a firm quote and nothing is charged until scope and price are confirmed. On the account server, chronology.generate is run first as a dry run that returns the page count and list price ($450 per case up to 500 pages) for the user to confirm.
- Which AI assistants can connect to Zicron?
- Any client that supports remote MCP servers over Streamable HTTP. For the account server, the client must also support MCP's OAuth sign-in. Claude (claude.ai, Claude Desktop, Claude Code), ChatGPT in developer mode and Cursor support this as of September 2026, but client menus and plan requirements change, so check each vendor's current documentation.