Using Orbrey with Claude (MCP)

Orbrey ships an MCP (Model Context Protocol) server so Claude, and any other MCP-aware client, can act on your household data directly. Ask Claude to plan a week of dinners, mark tasks done, or sync the meal plan to your grocery list, and it does so by calling Orbrey's API through a secure OAuth-protected endpoint.

Setup URL

Add this URL as a custom MCP connector in your client of choice:

https://mcp.orbrey.com/

The server is OAuth 2.1 with PKCE and Dynamic Client Registration. The first call from a new client opens the Orbrey consent page in your browser. Pick which household(s) to authorise and which scopes to grant, then Allow. The connector is good from that point on; revoke access any time from Settings, then Connected apps.

Every provider uses the same endpoint and adult-only household policy. The connector is designed to check all household memberships before returning or changing household data, and to refuse unless every membership is an adult account. Child, legacy kid, guest, local-only (a member without a login), unknown, or unreadable classifications are designed to fail closed. This uses Orbrey's stored classifications and does not independently verify age or scan free-text records.

Connecting Claude

Claude Desktop / Claude.ai web

Open Settings, then Connectors, then Add custom connector, paste https://mcp.orbrey.com/, click Add, and complete the browser-based consent flow.

Claude Code

Pre-registered loopback ports: 8080, 33418, 3334.

claude mcp add --transport http --callback-port 8080 \
  orbrey https://mcp.orbrey.com/

ChatGPT

ChatGPT supports MCP Apps using the same protocol. Add https://mcp.orbrey.com/ as a custom MCP server; the Orbrey widgets render in chat the same way they do in Claude. ChatGPT also shows Orbrey Home in its sidebar: a full-screen view of today's tasks and events with shortcuts for meals, groceries, and the pantry. It needs the Tasks and Calendar read scopes.

What you can do

The server exposes 50 tools across Orbrey's household areas. Each tool is scoped (read-only or write) and you choose which scopes to grant per household at consent time; your client only sees the tools those scopes allow.

Free-tier scopes

• Tasks: list occurrences, mark them done or open, skip them, and create, edit, or delete tasks.
• Calendar: list, create, edit, and delete events.
• Recipes: list, read, create, edit, and delete.
• Grocery: list items and lists, add, edit, tick off, move, merge duplicates, and delete.
• Shared lists: list, read, create, add and edit lines, and delete.
• Members and profile: list household members and update your own dietary details.
• Today snapshot: composite read of today's tasks + events for morning briefings.

Plus-tier scopes

• Pantry: list (with optional location and expiring-within-N-days filters), add, edit, consume, merge, and delete.
• Meal planning: read a week, add, edit, or remove meals, list missing ingredients, sync the week's recipes into the grocery list, and add a recipe's ingredients to it.

Inline widgets

Ten interactive views (built on the MCP Apps SDK) render alongside tool results in chat. Examples:

• “What's on today?” gives you a Today Agenda card with one-tap task completion.
• “Show this week's meal plan” gives you a 7-day grid with a Sync-to-grocery button.
• “What's in my pantry?” gives you a shelf view grouped by location with expiry alerts.
• “What's on the grocery list?” gives you the list grouped by category with an add-item form.

Which Claude clients render the widgets?

MCP Apps support is rolling out unevenly. The Orbrey server is spec-compliant, so when a client adds widget support, our widgets render automatically with no changes on our end.

Hosts that don't render widgets get a human-readable markdown summary instead of a raw JSON dump. For example, asking “list my recipes” in Claude Code returns a tidy bullet list, just without the swipeable cards you'd see in Claude Desktop.

Hosts that don't support MCP Apps yet still get the raw text result, so the integration degrades gracefully.

Safety, auth and data

• OAuth 2.1 with PKCE, Dynamic Client Registration (RFC 7591), Resource Indicators (RFC 8707), and RFC 9728 protected- resource metadata.
• Per-household, per-scope grants: every tool call checks the bearer token's household grant and required scopes.
• Row Level Security: Orbrey's database rules limit a signed-in person to the households they belong to.
• Rate-limited at the Cloudflare edge (60 calls / min per token).
• Plus-tier gating: pantry and meal-planner tools check the household's subscription before executing.
• Tool arguments the assistant sends are received by the server. The full conversation is not sent to Orbrey; the assistant's provider keeps its own copy under its own terms.

Troubleshooting

“No household is authorised for this MCP client”

Remove the connector in your MCP client and re-add it. The consent flow records which household(s) you authorised; if no household is selected, the server has nothing to act on.

“Tool requires an Orbrey Plus subscription”

The pantry and meal-planner tools are Plus features. Upgrade from Settings, then Billing, then retry. The free-tier tools work on any plan.

“Rate limit exceeded”

60 calls / minute per token. Wait a minute and retry; the limit resets continuously.

The widget shows “Connecting…” forever

Your client may not have MCP Apps enabled. Update Claude Desktop or switch to Claude.ai web; the tool will still work in text-only mode.

Disconnecting

Remove the connector in your MCP client AND disconnect the app from Settings, then Connected apps in the Orbrey app. The grant is what authorises the bearer token; disconnecting it stops all further tool calls from that client immediately.