AI quickstart
Let your AI assistant build the backend.
Extatic runs an MCP server. Connect Claude Code, Cursor, or any MCP client, and your assistant can create Apps and Collections, seed content, and write site code that calls Extatic correctly.
Create an access token
Sign in at app.extatic.io and open Access tokens (under your email in the sidebar). Create a token with Read and write access so the assistant can set things up. You can limit it to one App and choose when it expires.
Leave Allow reading end-user data off unless the assistant needs to see what your site's visitors submitted. Without it, the assistant only sees content you created.
Copy the token. It starts with ext_pat_ and is shown only once.
Connect your assistant
The server uses Streamable HTTP at https://app.extatic.io/mcp, with the token as a bearer token.
claude mcp add --transport http extatic https://app.extatic.io/mcp \
--header "Authorization: Bearer ext_pat_…"
{
"mcpServers": {
"extatic": {
"url": "https://app.extatic.io/mcp",
"headers": { "Authorization": "Bearer ext_pat_…" }
}
}
}
Keep the token out of version control. Most clients can read it from an environment variable instead.
Ask for a site
Use the server's build_static_site prompt, or ask in your own words:
Build a static blog for my bakery on Extatic. Create an App called “Crumb” that allows https://crumb.example.com, a posts Collection with a title, body, and publish date, and three sample posts. Then write an index.html that lists the posts.
What the assistant does
- Reads Extatic's getting-started guide, so its code uses the right URLs, headers, and error handling.
- Finds or creates your App and sets its allowed origins.
- Creates Collections with JSON Schemas, then seeds a few Items. Schema errors come back to the assistant so it can fix them.
- Reads the App's public id and Client API base URL, then writes site code that calls the Client API with
fetch.
What the assistant can't do
- Delete anything. Deletes stay in the dashboard.
- See your App's secret server key. It only gets the public id, which is safe in browser code.
- Go beyond your role: it acts as you, limited to the Apps and access you gave the token.
- Read your visitors' data, unless you allowed that when creating the token.
Every change it makes is logged with the token's name. Revoke a token any time under Access tokens.
Prefer to write the code yourself? The getting-started guide is the same one the assistant reads. AI tools can also read a summary of Extatic at /llms.txt.