FULLSCRIPT MCP & API
Build anything for your practice
For Fullscript provider accounts: connect your account to Claude, ChatGPT, or any MCP client in one command. Ask questions, draft plans, and automate follow-ups in plain language — with a REST API underneath when you want to build your own.
1 command
to connect an assistant
24 tools
on the MCP server
Per provider
scoped data access
REST too
when you want to build
$ claude mcp add fullscript https://mcp.fullscript.dev✓ connected · 24 tools available> which patients lapsed on refills this month?● fullscript.refill_adherence({ period: "last_30_days" })← 12 patients · top: Magnesium Glycinate● fullscript.draft_followups({ patients: 12 })12 drafts are ready for review in FullscriptYour practice runs on Fullscript. Your assistant should see it
Reporting lives in exports, follow-ups live in your head, and the AI assistant you already use every day can’t see your dispensary. The Fullscript MCP server hands it your patients, plans, orders, and reports — so you can just ask.
HOW IT WORKS
From switch-on to first question
Enable
Your account owner flips one switch in settings.
Activate
Each provider opts in and gets access scoped to their data.
Connect
One command points your assistant at the MCP server.
Ask
Reports, drafts, follow-ups — in plain language.
MCP FIRST
What your assistant can do once it’s connected
Twenty-four MCP tools cover the same ground as your provider account. Ask in plain language, or call the same capabilities over REST when you’d rather write code.
Ask about your practice
"Which patients lapsed on refills this month?" Your assistant queries the MCP server and answers from your own account data.
Draft treatment plans
"Draft a follow-up plan for Dana based on her last labs." The draft lands in Fullscript for you to review and send.
Reporting on request
Ask for adherence, revenue, or product mix and get it back as a table or a CSV — no exports, no spreadsheets.
Automate the follow-through
Have your assistant queue refill nudges and post-visit check-ins, then confirm before anything goes out.
Or build it yourself
Every MCP tool has a REST equivalent, so scripts and internal tools use the same endpoints your assistant does.
Enabled by your account owner, scoped to each provider
The account owner turns the feature on, each provider activates it individually, and every provider sees and acts on only their own data. You’re responsible for being a good steward of your patient data and the actions taken in your account — including making sure any systems you connect comply with applicable laws and regulations.
Owner enabled
Per-provider activation
Scoped to your own data
MCP first, REST too
Provider accounts only
$ claude mcp add fullscript \ https://mcp.fullscript.dev✓ Connected as Dr. Amara Osei 24 tools · patients, plans, orders, reports// works with any MCP client — Claude,// ChatGPT, Cursor, or your own agentQUICKSTART
Three steps to a connected assistant
- STEP 1
Owner enables the feature
One switch, at the account level.
Settings → Developer → Enable MCP & API - STEP 2
Activate as a provider
Opt in and get access scoped to your own data.
Profile → API access → Activate - STEP 3
Point your assistant at the server
Then just ask. REST is there when you want to build.
claude mcp add fullscript https://mcp.fullscript.dev
Connect your assistant to your practice
The Fullscript MCP server for provider accounts is coming soon. Join the waitlist and we’ll reach out when it’s your turn.
Pairs with
Most integrations ship with two or more products working together.