## What this is

Curogram MCP v1 — a Model Context Protocol server scoped to **messaging** on Curogram, plus the channel + host config to wire it into the agent's MCP stack. This is the first cut: it covers patient/team messaging and read-only patient lookups so the agent can triage and respond to inbound Curogram threads.

## Tools (8)

**Messaging (5)**
- List conversations / threads
- Read a conversation's messages
- Send a text message (confirm-gated, see Safety)
- Mark conversation read / manage thread state
- Search / locate a conversation

**Read-only patient (3)**
- Look up a patient
- Read patient profile / contact details
- Read patient's conversation linkage

## Auth approach

- Programmatic login: username/password sign-in that captures the session **cookie + XSRF token**.
- **Auto-relogin** on session expiry / 401 so long-running agent sessions don't silently break.
- **CDP fallback**: if programmatic login is blocked, fall back to a Chrome DevTools Protocol browser session to establish auth, then reuse the harvested cookies.

## Safety

- `send-text` is **confirm-gated** — no message goes out without explicit confirmation.
- **TCPA consent check** before sending: outbound texting is gated on the patient's consent state.
- **No PHI logged** — patient-identifying content is kept out of logs.

## Tests

- mcp-config suite: **12/12 green** (channel + host + golden config).
- Server boots clean on a smoke run.

## Deploy

Deploy is a **separate, gated step** — this PR only adds the server + config. No deployment, no server start, no merge implied by this PR.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>