Bring your own agent

OpenCare works with Grok, Claude, ChatGPT, OpenClaw, Cursor — anything that speaks MCP or can call a REST API. Your key sees your circles and nothing else. Free.

1 · Get your API key (2 minutes)

Sign in at opencare.world/care (free account) and create or join a circle.
Go to Profile → API Keys → Generate.
Copy the oc_... key — it's shown once. Revoke it anytime from the same page.

Keys are scoped to your account: they can only see and act on circles you belong to. Coordinator-only actions stay coordinator-only through the API.

2 · Connect an agent (MCP)

The MCP server lives at https://opencare.world/mcp. Two ways to authenticate — a standard bearer header, or (for connector UIs without a header field) your key in the URL:

https://opencare.world/mcp            + header  Authorization: Bearer oc_YOURKEY
https://opencare.world/mcp/oc_YOURKEY   (key-in-URL form)

Grok (web, iOS, Android)

grok.com/connectors (or app: Settings → Connectors) → New Connector → Custom → paste the key-in-URL form above. Then just talk: "What tasks are open in my circle?"

Claude

claude.ai → Settings → Connectors → Add custom connector → paste the key-in-URL form. In Claude Code: claude mcp add opencare https://opencare.world/mcp -H "Authorization: Bearer oc_..."

ChatGPT

Settings → Connectors (developer mode) → add the key-in-URL form. Or build a Custom GPT with Actions against the REST API below.

OpenClaw

{ "mcp": { "servers": { "opencare": {
  "url": "https://opencare.world/mcp",
  "transport": "streamable-http",
  "headers": { "Authorization": "Bearer ${OPENCARE_KEY}" }
} } } }

Cursor / VS Code / anything MCP

Add a remote MCP server with the URL and bearer header — standard streamable HTTP, no session state required.

Your agent gets 12 tools: list circles and tasks, create and assign tasks (including to helpers), log and search visits, read helper replies, create helper link pages, and ask_care_agent — an AI that answers questions about the visit history with dates cited.

3 · Or use the REST API directly

curl https://opencare.world/api/v1/circles \
  -H "Authorization: Bearer oc_YOURKEY"

Method	Path	What it does
GET	/api/v1/circles	List your circles
GET	/api/v1/circles/{id}	Circle detail
GET	/api/v1/circles/{id}/summary	Overview: tasks, members, activity
GET	/api/v1/circles/{id}/tasks	List tasks (?status=active&priority=high)
POST	/api/v1/circles/{id}/tasks	Create a task (assigned_contact_id → assign to a helper)
PATCH	/api/v1/circles/{id}/tasks/{taskId}	Update / complete a task
GET	/api/v1/circles/{id}/visits	Visit log (?q= text match)
POST	/api/v1/circles/{id}/visits	Log a visit
POST	/api/v1/circles/{id}/ask	AI care agent: ask about visit history
GET	/api/v1/circles/{id}/messages	Helper replies (notes, photos)
GET	/api/v1/circles/{id}/contacts	List helpers
POST	/api/v1/circles/{id}/contacts	Add a helper (coordinator only)
POST	/api/v1/circles/{id}/share-links	Create a helper's no-login page
PATCH	/api/v1/circles/{id}/share-links/{linkId}	Set page language (en/es)
DELETE	/api/v1/circles/{id}/share-links/{linkId}	Revoke a link
GET	/api/v1/circles/{id}/resources	Local resources

All responses are JSON as { data: ... } or { error: ... }. Write endpoints need a key with write scope (the default).

Guardrails your agent will hit (on purpose)

Marking a task completed or cancelled requires confirm: true — no accidental bulk-closing by an over-eager agent.
Every request is scoped to the key's account. A key that isn't in a circle gets a 403 — there is no flag to turn that off.
The AI care agent is limited to 50 questions per account per day.
Coordinator-only actions (adding helpers, revoking links) stay that way.

Questions, ideas, something broken?

We're builders and we answer. Reply to @FotiosM on X or email updates@opencare.world. OpenCare is free and built in public — if your agent needs an endpoint we don't have, tell us and we'll probably ship it.