Grok Bot with Last EHR

Connect native Grok Bot to Last's Work MCP service so it can read a bounded synthetic chart, draft a follow-up request, and check the saved result after a human approves it in Last. Grok supplies the assistant; Last supplies the tools, durable work state, separate review, and verified FHIR Task receipt.

What you can use today

The service supports one workspace, one configured reviewer, and one process. An operator must allow each exact OAuth client/user pair. Each assistant owns its own work; a new identity cannot retrieve another assistant's jobs. A shared Bot template does not create a Last workspace, enroll a user, or supply the author's sign-in.

This guide covers native Grok Bot, not a verified integration with Grok chat at grok.com. The separate published @lastehr/mcp package exposes chart tools; this Work service is the checkout's durable draft-and-review interface.

Prepare a Work deployment

Follow Hosted Synthetic Work or the OVHcloud Work Pilot runbook. Before connecting Grok, have:

• A public HTTPS Work MCP URL and reachable OAuth discovery endpoints.
• A registered public PKCE assistant client, the exact Cursor cloud callback, and permission to request work:assistant offline_access.
• An operator who can verify and allow the intended assistant user's exact client ID/subject pair, distinct from the reviewer subject. A new user's subject may only become known after their first provider sign-in.
• A separate human-owned browser signed into Last's configured reviewer.

The hosted guide documents the Auth0 API grant, Google connection setup, and identity checks. Keep the reviewer's sign-in in that human-owned browser. Grok's cloud computer and Last's reviewer browser have different jobs.

Add the connection

Sign into Cursor Agents with the same account used by Grok Bot. Open its MCP dropdown and add a personal HTTP server. In the web configuration editor, use this server map, replacing both placeholders. The map is not wrapped in a mcpServers property:

{
  "Last Work Native": {
    "url": "https://YOUR_WORK_ORIGIN/mcp",
    "auth": {
      "CLIENT_ID": "YOUR_PUBLIC_ASSISTANT_CLIENT_ID",
      "scopes": ["work:assistant", "offline_access"]
    }
  }
}

Use the registered public client ID, with no CLIENT_SECRET or bearer header. Choose Connect and finish the provider login and consent using the intended assistant account. Then return to native Grok Bot and check Connect apps → Installed for that connection and its four Work tools.

If consent succeeds but Last rejects access, the operator must verify the actual provider user and client pair and add it to Last's allowlist. Then reconnect the same connector. A successful provider login does not enroll that user in Last.

In the observed test, the native Authenticate control did not open the provider page. Connecting the same configuration through Cursor web completed authorization; native Grok Bot then used it. If that native button does nothing, use the web Connect route for the existing connection. An Installed badge alone does not establish authenticated tool access. Cursor personal MCP setup, Static OAuth configuration, Grok Bot app connections

Ask for work and review it

Ask in the connected native Bot:

Use Last Work Native to look at Alex's synthetic chart and draft a follow-up task for me to review.

The configured MCP instructions guide the chart read and proposal. Grok writes the description; you do not need to supply JSON, a submission key, or an expected result. Last exposes read_work_context, propose_work, get_work, and cancel_work. It exposes no assistant approval or direct-save tool.

Open the draft in Last's separate reviewer browser. Inspect the exact resource and source, then approve or decline it yourself. After approval, return to the same Grok conversation and ask:

Approved. Did it save?

Grok should use its retained Work ID to check the result. Saving a Task records a request; it does not contact a patient or complete care.

Recorded Grok walkthrough

Watch the 43-second walkthrough · Read the verification record

This silent video is edited from actual screenshots of the October 25, 2026 test in Grok Bot 0.75.8. It is not a continuous recording. The human approval happened between captures; the click was not recorded or recreated.

The first request was “In Last, look at Alex's synthetic chart and draft a follow-up task for me to review.” Grok initially could not find the connector named Last. The operator clarified that its name was Last Work Native, checked its status, and resumed the ordinary request. This was not first-try connector discovery. The operator supplied no draft wording, tool arguments, submission key, expected hash, or expected result.

Independent read-only store and FHIR checks found zero matching Tasks before human approval and exactly one afterward: Task/1053, version 1. The saved fields matched the exact resource approved in Last. Grok's chat summary omitted a reviewer-name sentence from that resource; the resource displayed in Last governed the approval.

The native UI did not expose raw MCP payloads or a proposal hash. The evidence therefore correlates the observed conversation with independently checked stored state. OAuth authorization completed through Cursor web and was used by native Grok Bot. An Auth0 refresh exchange was observed, but a native read after the original access token expired remains unverified.

All chart data is invented. This demonstration does not establish clinical correctness, real-patient authorization, HIPAA readiness, public self-service, or compatibility with other assistant clients.