---
title: Integrations | Nextvisit
description: API keys, OAuth, and MCP for the Nextvisit workspace. Bring your own tools and AI assistants onto the same clinical surface.
url: "https://nextvisit.ai/integrations"
type: static
generatedAt: "2026-09-21T03:14:00.496Z"
---

Integrations
# Bring your own tools, AI assistants, and pipelines.

API keys, OAuth, and MCP share one workspace-scoped view of patients, encounters, notes, and codes, with PHI staying inside the boundary.

### API keys

Workspace-scoped REST keys. Per-key scopes, full audit log.

 - Workspace-scoped, never cross-tenant
- Per-key scopes for read, write, and admin paths
- Audit log on every issued, rotated, or revoked key
  [Read API docs](/help/api-keys)
### OAuth

OAuth 2.0 for delegated third-party access.

 - Authorization code flow with PKCE
- Granular scope review before consent
- Refresh and revocation from Settings
  [Open Settings](#)
### MCP

Nextvisit runs a Model Context Protocol server. Typed tools, same workspace scope.

 - Claude, ChatGPT, local LLMs
- Typed tools for patients, encounters, notes, codes
- Same workspace scope as API keys and OAuth
  [Read MCP guide](/help/mcp-server)
Nextvisit exposes the workspace as an MCP server. An assistant connects once and reads patients, encounters, notes, and codes through typed tools, under the same workspace scope as API keys and OAuth.

A clinician can point Claude, ChatGPT, or a local model at the workspace and ask questions against real chart data. Tool calls return structured JSON.


*Sample MCP tool call*

```
// Assistant invokes a Nextvisit MCP tool
query_encounters({
  patient_id: "pat_018f...c1",
  range: { from: "2026-01-01", to: "2026-05-01" },
  include: ["note", "codes", "peer_review"]
})

// Returns
{
  "encounters": [
    {
      "id": "enc_a1b2",
      "date": "2026-04-18T14:32:00Z",
      "status": "signed",
      "codes": ["F33.1", "F41.1"],
      "note": "..."
    }
  ]
}
```

Illustrative shape, not the verified call signature. [Read the MCP server guide](/help/mcp-server) for the endpoint URL, the live tool list, and connection steps for Claude, ChatGPT, and local LLM clients.


*curl: list signed encounters for a patient*

```
# List signed encounters for a patient over a date range
curl -sS \
  -H "Authorization: Bearer nv_live_8f2c...41a" \
  -H "Accept: application/json" \
  "https://api.nextvisit.ai/v1/encounters?patient_id=pat_018f...c1&status=signed&from=2026-01-01"

# Response (truncated)
{
  "data": [
    {
      "id": "enc_a1b2",
      "signed_at": "2026-04-18T14:42:11Z",
      "provider_id": "prv_77a3",
      "codes": ["F33.1", "F41.1"]
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjUwfQ"
}
```

Illustrative endpoint and key shape. The live API reference covers pagination, rate limits, and the full resource list.

### Pocket

The heypocket.com hardware recorder posts each recording on completion. AriaMD generates a note in the assigned template, like a live session.

Say the patient name and date of birth in the first minute.

### Plaud AI

Plaud AI pin and Plaud Note recordings sync into the workspace. Useful if you already carry one for personal capture.

Same convention: name and DOB at the top of the recording.

[See the four ways to start a note on the how-it-works page](/how-it-works)

FHIR R4 and HL7 v2 cover most stacks. Partner integrations cover the rest. Copy-out plus fax handles the long tail. Destination list, bundle layout, and live push state are on the features page.

[See EHR integration on the features page](/features#ehr)
              See it on your workflow
## One mock visit, one note in your template.

We run a mock session, draft the note, and show the claim. No slides.
  [Book a demo](https://nextvisit.cal.com/ryan/demo) [Talk to sales](mailto:hello@nextvisit.ai)     Live in 2 weeks or less   BAA signed by default