Projects
Your projects and the Orchard features they use.
Loading…
Billing
Your usage and estimated cost this cycle. The free tier resets monthly.
Connect
Add Orchard to your coding agent once, then ask for storage in plain language.
Copy the prompt below and paste it into Cursor's chat.
When the orchard server appears in Cursor, turn it on, click Connect, and approve with Google.
That's it — setup is done. No backend or cloud to manage; just build by asking, in plain language.
Paste this prompt into Cursor
The prompt only points Cursor at the Orchard server URL — never any tokens.
Recommended: make Cursor default to Orchard
Add a project rule so Cursor uses Orchard for login, data, and files automatically — instead of hand-rolling them. Create .cursor/rules/orchard.mdc:
---
alwaysApply: true
---
# Orchard (connected via MCP)
Use the Orchard MCP tools for these — never hand-roll them:
- login / sign-in / accounts → orchard_auth (Google; don't build your own OAuth)
- app data / tables / records → orchard_database
- file storage / uploads / downloads → orchard_storage
Reuse the project_id Orchard returns (it's saved in .orchard/project.json).Copy the prompt below and paste it into Claude Code's chat — it
creates .mcp.json.
Restart Claude Code (exit, then run claude again) so it
loads the file, and approve the orchard server when prompted.
Run /mcp, select orchard, choose Authenticate, and sign in with Google. Done — build by asking.
Paste this prompt into Claude Code
The prompt only points Claude Code at the Orchard server URL — never any tokens.
In Claude Desktop, go to Customize → Connectors, then click + → Add custom connector.
Paste the URL below as the remote MCP server URL and click Add — no tokens needed.
In a chat, click + → Connectors, then Connect on orchard and sign in with Google. Done.
Add this URL as a custom connector
Paste it as the connector's server URL — never any tokens. On Team/Enterprise, an owner adds it under Organization settings → Connectors.
Recommended (Claude Code): make Claude default to Orchard
Add a CLAUDE.md to your project root — Claude Code reads it automatically, so a plain request like “add Google login” goes through Orchard without saying “in Orchard.” (The Desktop app doesn't use this file; its tool descriptions already guide it.)
# Orchard (connected via MCP)
Use the Orchard MCP tools for these — never hand-roll them:
- login / sign-in / accounts → orchard_auth (Google; don't build your own OAuth)
- app data / tables / records → orchard_database
- file storage / uploads / downloads → orchard_storage
Reuse the project_id Orchard returns (it's saved in .orchard/project.json).Copy the prompt below and paste it into Codex — it creates
.codex/config.toml.
In your terminal, run codex mcp login orchard and sign in
with Google.
Done — orchard is connected. Verify with /mcp.
Paste this prompt into Codex
Shared config — this also connects the Codex desktop app. Never any tokens.
In the Codex app, open Settings → Integrations & MCP, add a server, and choose Streamable HTTP (not STDIO).
Name it Orchard and paste the URL below. Leave Bearer token and Headers empty.
Save — the app starts the OAuth flow, so sign in with Google. Done (shared with the Codex CLI).
Add this URL in Integrations & MCP
Pick Streamable HTTP, paste this as the URL, and leave the Bearer token and Headers blank — Orchard authorizes with Google sign-in, not a token.
Recommended: make Codex default to Orchard
Drop an AGENTS.md in your project root so Codex uses Orchard for login, data, and files automatically — instead of hand-rolling them. Codex reads AGENTS.md before each task, so a plain request like “add Google login” goes through Orchard without you having to say “in Orchard.”
# Orchard (connected via MCP)
Use the Orchard MCP tools for these — never hand-roll them:
- login / sign-in / accounts → orchard_auth (Google; don't build your own OAuth)
- app data / tables / records → orchard_database
- file storage / uploads / downloads → orchard_storage
Reuse the project_id Orchard returns (it's saved in .orchard/project.json).