Sikka MCP speaks the open Model Context Protocol over Streamable HTTP — the same tool catalog and the same live practice data, reachable from Claude Code, Codex, or any MCP client you build.
"How many patients does the office have?"
Your practice has 11,539 patients on record.
"How many patients does the office have?"
Your practice has 11,539 patients on record.
"How many patients does the office have?"
Your practice has 11,539 patients on record.
Same question, same server, same answer — the client is interchangeable.
Two assistants, the same Sikka MCP connection: one answers the phone, one answers "how are we doing." Both run live tool calls, not a script.
A patient asks for an opening. The assistant checks the live schedule, matches the chart, and writes the confirmed appointment back to the PMS — no hold music.
Riverside Dental — a fictional practice used for this demo.
The same connection answers performance questions — production trends, per-provider breakdowns, no-show risk — and keeps watching after the conversation ends.
Riverside Dental — a fictional practice used for this demo.
The same server behind both demos above — here's how to point your own client at it.
Setup{
"transport": "http",
"url": "https://mcp.sikkasoft.com/mcp",
"headers": {
"App-Id": "your_app_id",
"App-Key": "your_app_key",
"Office-Id": "D1000"
}
}
One connection, one practice by default — or omit Office-Id and pass it per call to serve multiple practices from a single partner connection.
Fetch records — appointments, patients, providers, transactions, claims, treatment plans, and more.
Aggregate, group, join, or trend across two data types in one query.
Named performance metrics — production, collections, case acceptance, and 80+ more.
Create or update records. Always previews first — nothing writes without an explicit confirm.
Patient insurance eligibility checks with automatic payer matching.
Full patient journey — appointments, transactions, plans, claims, and notes in one call.
Available appointment slots by provider, operatory, or date range.
Field and endpoint reference for building queries against practice data.
Compatibility and status-value reference across 50+ practice management systems.
Practice data-sync status and SPU health monitoring for partners.
Async CSV export for datasets too large for a single call — 2M+ records.
List every practice (office_id) a partner connection can access.
Your secret_key is looked up and held server-side — it's never issued to a client, and never expires you out of a connection.
Point any Streamable-HTTP MCP client at your credentials and start asking — coreapis, practicequery, and the rest are live from the first call.
Riverside Dental and every name in these conversations are fictional. The tool calls and response shapes match real Sikka MCP behavior — nothing here is a transcript of an actual patient or practice.