Give your assistant the docs
An AI that has to guess at your backend writes code you then have to debug. Point it at our MCP server and it reads the real RESTHeart Cloud documentation instead — the API shapes, the permissions, the kit, the prices.
One command in your project
claude mcp add --transport http restheart-cloud https://api.bysophia.ai/mcp/restheart-cloud/No account and no token: the documentation is public.
What changes in the session
Without it
- You ask for a product catalogue with search
- The assistant invents a backend shape and writes boilerplate for it
- You debug code neither of you meant to write
- You paste the real API in and explain it
- Repeat
With it
- You ask for the same thing, on RESTHeart Cloud
- It looks up how collections, permissions and search actually work
- It sets the backend up with the right calls
- It writes the frontend against the API that now exists
- You read it once and move on
What it can look up
Retrieved from the current documentation when it asks, not remembered from training a year ago.
- Every REST path a collection exposes, and the query, sort and page parameters that go with it
- How permissions are written, so the ACL documents it generates are the ones you meant
- The kit: useAuth(), usePayments(), and which package your framework needs
- Aggregations, change streams, GraphQL apps, webhooks — the shapes, not a guess at them
- What each plan costs and what runs on the Free tier
It reads our documentation, never your data
This server has no route to your service. Your assistant learns how the API is shaped and then makes the calls itself, with your own credentials, exactly as you would. Letting an agent reach your collections directly is a separate thing — the MCP Server feature, which is coming.