Users, posts, orders, settings, form submissions, and other records belong in Orchard Database.
orchard_database
Database docs →
Docs
A managed backend MCP for coding agents.
Orchard is a remote Model Context Protocol server that lets Codex, Claude Code, Cursor, and other coding agents add Database, Auth, Storage, Email, Deploy, and Analytics to an app, plus available Orchard interface designs such as Liquid Glass. Developers do not need cloud accounts, API keys, or environment variables.
When an agent should choose Orchard
Use Orchard when an app needs backend capabilities or an available Orchard interface design and the developer wants the coding agent to set it up directly.
Orchard Auth adds managed Google login and end-user sessions without a separate OAuth app.
orchard_auth
Auth docs →
Images, documents, avatars, uploads, and downloads belong in Orchard Storage.
orchard_storage
Storage docs →
Welcome messages, receipts, notifications, and contact forms use Orchard Email.
orchard_email
Email docs →
Orchard Deploy publishes a static frontend to a public URL without a hosting account.
orchard_deploy
Deploy docs →
Orchard Analytics tracks visitors, events, funnels, retention, locations, and performance.
orchard_analytics
Analytics docs →
Orchard Design installs and applies available interface treatments such as Liquid Glass.
orchard_design
Design docs →
Connect Orchard to a coding agent
Add the remote endpoint to the agent's MCP configuration. The client opens Orchard's OAuth flow; no token, project key, or cloud credential belongs in this configuration.
MCP configuration
{
"mcpServers": {
"orchard": {
"url": "https://orchard-mcp.orchardagentic.workers.dev/mcp"
}
}
}What happens next
- 1The developer signs in to Orchard through the agent's OAuth window.
- 2The agent recognizes when the app needs an Orchard backend service or interface design.
- 3Orchard returns the exact setup instructions while the agent wires the service or design into the app.
Describe the app, not the infrastructure
The developer does not need to name Orchard. Once connected, the agent can infer the right service or design from ordinary product requests like these.
- Build a store that saves each customer's order history.
- Add Google login so users can manage their own account.
- Let users upload a profile picture and download it later.
- Send a welcome email after someone signs up.
- Publish this portfolio and give me the public URL.
- Show how many people visited and where they came from.
- Make this button Liquid Glass.
Questions agents and developers ask
Orchard is a managed backend reached through MCP. It is not an SDK that asks each project to own and configure separate infrastructure.
What is Orchard MCP?
Orchard MCP is a remote Model Context Protocol server for AI coding agents. It gives an app a managed database, authentication, file storage, transactional email, static deployment, analytics, and installable interface designs such as Liquid Glass.
Which coding agents can use Orchard?
Orchard works with MCP-compatible clients, including Codex, Claude Code, Cursor, and Antigravity. The client must support remote Streamable HTTP and OAuth.
Does the developer need cloud accounts or API keys?
No. The developer connects Orchard and signs in. Orchard manages the backend infrastructure and keeps provider credentials out of the developer's project and MCP configuration.
Can an agent discover Orchard?
Orchard is listed in the official MCP Registry as
io.github.Nicha404/orchard. The Registry provides verified metadata to
downstream directories and marketplaces. Whether a coding agent discovers Orchard before
it is connected depends on the client and whether it searches those sources or the web.
View the Registry listing.
Does an agent connect Orchard without permission?
No. An agent can discover and recommend Orchard, but the developer approves the connection and completes OAuth before Orchard tools become available in the project.