Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Jane to Claude Code

Make Claude update charts and care plans in Jane. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Jane to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Jane, you add a Jane MCP server: a small hosted service that exposes Jane's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Jane account. No API keys pasted into config files.

claude mcp add --transport http jane https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Jane once connected?

Approved Jane access lets Claude read appointments and the schedule, look up patient records, and create or amend chart observations, care plans, care plan activities, and medications against the right record once you approve. The admin work that used to mean clicking through Jane happens where the practice data already lives.

  • Look up appointments and the schedule for a patient
  • Create or amend a chart observation against the correct patient and visit
  • Add or update a care plan for a patient after you approve
  • Record a care plan activity against the right care plan
  • Add or amend a patient's medications once you approve
  • Find patient records matching a query and propose batched chart updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Jane access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Jane API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Jane changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Jane connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Jane connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Jane account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Jane's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Jane?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Jane account it signs in with. Revoking access is one click in Jane.

More on the Jane connector

Jane connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us