StaticOwl in Claude Code
Read the connect guide → · HTTP API reference · Or use Claude Desktop
Connect StaticOwl to Claude Code and you can drive your CMS from the terminal — create and edit pages, publish and build, upload media, run an SEO audit, add redirects — by asking in plain language.
Add the connector
Add the server from your terminal:
claude mcp add --transport http staticowl https://app.staticowl.com/api/mcp
Then open Claude Code and run /mcp, pick staticowl, and choose Authenticate to sign in through your browser. Run claude mcp list any time to confirm it's connected.
Use --scope user to make it available in every project, or --scope project to keep it to the current repo.
There's no key to paste — you authenticate in the browser.
Once sign-in finishes, start a chat and ask it to list your sites to confirm the connection.
Choose your toolset
StaticOwl exposes 334 tools across 12 toolsets. When you add the connector you pick a preset:
- core — a tight starter set.
- recommended — the default, day-to-day tools. This fits most people.
- all — the full 334 tools.
The 12 toolsets group tools by the work they do: sites; content; content types; templates and themes; media; SEO; internal links; builds and releases; domains and redirects; forms and integrations; authoring; and access and workflow.
What you can do
Ask in plain language. A few examples:
Draft a page
In my site, write a 500-word blog post about why static site generators are having a renaissance. Match the site's voice, add SEO metadata and a few relevant tags, and save it as a draft. Show me the draft before you save.
Publish and build
Publish the "Pricing" page and run a build. Tell me the build status and the live URL when it's done.
Run an SEO audit
Audit my site's SEO. List the pages missing a title or description and suggest fixes. Don't change anything yet — show me the list first.
Add a redirect
Add a 301 redirect from /old-pricing to /pricing, then confirm it's in the redirect list.
Upload media with alt text
Upload a hero image from this URL, generate descriptive alt text for it, and add it to the "About" page.
Safe by design
An assistant works through the same steps you would.
- Edits start as drafts. Nothing is public until you publish.
- Publishing is deliberate. Content goes live only when it is published and the site is built. You decide what gets published.
- Changes are reviewable and reversible. Every change keeps history, and a build can be rolled back.
Use the HTTP API directly
The same surface is available over HTTP, which is useful for scripting or debugging. This path uses an account API key — it is not how you connect a client (that is OAuth):
# Health check
curl https://app.staticowl.com/api/health
# List the available MCP tools
curl -X POST https://app.staticowl.com/api/mcp \
-H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
See the HTTP API reference for the full surface.
FAQ
Do I need an API key?
No. You add the connector and sign in through your browser (OAuth). There is no key to copy or paste. An account API key is only needed if you call the HTTP API directly.
What's the difference from Claude Desktop?
Same MCP endpoint and the same tools. Claude Code is the terminal-native client; Claude Desktop is the desktop app. Both connect the same way — add the connector, then sign in with OAuth. Use whichever fits how you work.
Should I use user scope or project scope?
Add with --scope user to make the connector available in every project. Add with --scope project to keep it to the current repo. Pick based on whether you want it everywhere or only in one codebase.
Can my team use it?
Yes. Each person adds the connector and signs in with their own account. The assistant has the same permissions that person has — nothing more.
How do I confirm it's connected?
Run claude mcp list to see staticowl, or run /mcp inside Claude Code to pick it and view its tools. Then ask it to list your sites.
See also
- Connect guide — step-by-step for every client.
- HTTP API reference.
- What the AI features do.
Questions? Email support@staticowl.com.