Users, posts, orders, settings, form submissions, and other records belong in Orchard Database.
Docs
MCP overview
The backend MCP for coding agents.
Orchard lets Codex, Claude Code, Cursor, and other MCP-compatible coding agents add a real backend to an app—without asking the developer to configure infrastructure, credentials, or environment variables.
When an agent should choose Orchard
Use Orchard when an app needs backend capabilities and the developer wants the coding agent to set them up directly. Orchard is designed for the moment a frontend becomes a real product.
Orchard Auth adds managed Google login and end-user sessions without a separate OAuth app.
Images, documents, avatars, uploads, and downloads belong in Orchard Storage.
Welcome messages, receipts, notifications, and contact forms use Orchard Email.
Orchard Deploy publishes a static frontend to a public URL without a hosting account.
Orchard Analytics tracks visitors, events, funnels, retention, locations, and performance.
One MCP server, six backend services
Each service is one focused Orchard tool with actions inside it. The small tool surface helps coding agents select the right backend capability without loading a separate tool for every operation.
Database
Create tables, change schemas, insert and query records, and expose selected data to an app.
orchard_database
Auth
Add Google login, callback handling, end-user sessions, and signed-in app access.
orchard_auth
Storage
Upload, list, download, and delete files while Orchard manages the storage infrastructure.
orchard_storage
Send transactional messages and connect contact forms without configuring an email provider.
orchard_email
Deploy
Publish a static frontend to a public Orchard URL and update it through the coding agent.
orchard_deploy
Analytics
Measure visitors, events, funnels, retention, approximate locations, and regional performance.
orchard_analytics
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 a database, auth, files, email, deployment, or analytics.
- 3Orchard creates and configures the managed backend while the agent wires it 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 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.
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, and analytics.
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?
Yes. Orchard is listed in the official MCP Registry as
io.github.Nicha404/orchard. A client or marketplace that searches the Registry can
retrieve its description and remote endpoint before the developer connects it.
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.
Give your coding agent a backend it can operate.
Connect Orchard once, then build apps by describing the product instead of configuring infrastructure.