Projects
Your projects and the Orchard features they use.
Loading…
Billing
Your usage and estimated cost this cycle. The free tier resets monthly.
Connect
You only need to connect Orchard once. Ask for backend features in plain language.
Copy the prompt below and paste it into the Cursor CLI
(cursor-agent) — it sets up the server and a project rule.
When the orchard server appears, 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 the Cursor CLI for each project folder where you want to use Orchard.
Copy the prompt below and paste it into Cursor's chat — it sets up the server and a project rule.
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 for each project folder where you want to use Orchard.
Copy the prompt below and paste it into Claude Code's chat — it
creates .mcp.json and a CLAUDE.md rule.
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 points Claude Code at the Orchard server URL and adds a CLAUDE.md rule — never any tokens.
In Claude Desktop, go to Customize → Connectors, then click + → Add custom connector.
Add the Orchard rule below to your project's instructions so Claude uses Orchard for supported backend services.
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.
Add this Orchard rule to your project instructions
On Team/Enterprise, an owner may need to add Orchard under Organization settings → Connectors first.
Copy the prompt below and paste it into Codex — it creates
.codex/config.toml and an AGENTS.md rule.
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 — also connects the Codex desktop app, and adds an AGENTS.md rule. Never any tokens.
In the Codex app, open Settings → Integrations & MCP, add a server named Orchard, and choose Streamable HTTP (not STDIO).
After adding the Orchard MCP server in Codex Desktop, add the project instruction below.
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.
Create AGENTS.md in the project root
If it already exists, merge this section into the existing file without removing other project instructions.
Copy the prompt below and paste it into Antigravity — it adds the MCP server and a project instruction.
In Antigravity CLI, run /mcp to verify the orchard server, and complete Google sign-in if prompted.
That's it — setup is done. No backend or cloud to manage; just build by asking, in plain language.
Paste this prompt into Antigravity CLI for each project where you want to use Orchard.
Copy the prompt below and paste it into Antigravity — it adds the MCP server and a project instruction.
Verify the orchard server in Agent Panel → MCP Servers, and complete Google sign-in if prompted.
That's it — setup is done. No backend or cloud to manage; just build by asking, in plain language.
Paste this prompt into Antigravity Desktop IDE for each project where you want to use Orchard.