Integration · MCP

StaticOwl in Claude

Connect StaticOwl to Claude and work on your sites from a chat. Claude can list your sites, create and edit content, run an SEO audit, publish and build, add a redirect, and manage domains — working through the same steps you would. It works in Claude on the web and on desktop.

Add the connector

You add StaticOwl once, then sign in through your browser. There is no key to copy or paste.

Open Settings → Connectors.
Click Add custom connector.
Paste the connector URL: https://app.staticowl.com/api/mcp
Click Add, then Connect, and sign in to StaticOwl when the browser window opens.

Claude lists the StaticOwl tools once sign-in finishes. Start a new chat and ask it to list your sites to confirm. This works in Claude on web and desktop — no bridge, no key.

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 the 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. You can change the preset later from the connector settings.

What you can do

Ask Claude in plain language. A few prompts to start with:

Create a page

In my main site, create a new page titled "About us" with a short intro paragraph and a slug of about-us. Leave it as a draft for now and show me the result.

Publish and build

Publish the "About us" page, run a build, and tell me when it is live. If the build fails, show me why.

Run an SEO audit

Run an SEO audit on my main site. List the pages with missing titles or descriptions, and draft fixes for the three worst ones.

Add a redirect

Add a 301 redirect from /old-pricing to /pricing, then confirm it is in the redirect list.

Upload media with alt text

Upload the image at this URL to my media library, generate descriptive alt text for it, and tell me the media ID I can reference.

Safe by design

An assistant works through the same steps a person does. You stay in control of what goes live:

Edits start as drafts. Content goes live only when it is published and the site is built.
You decide what gets published. Claude makes changes and reports back; publishing is a deliberate step.
Changes are reviewable and reversible. Changes keep history, and a build can be rolled back.

Curl it directly

The MCP server is also HTTP-addressable, so you can call it from a script or the command line. These requests use an account API key from your StaticOwl account settings — the client connect flow above uses browser sign-in instead, with no key to paste.

# Health check
curl https://app.staticowl.com/api/health

# Who am I?
curl -H "Authorization: Bearer $KEY" https://app.staticowl.com/api/access/me

# List the MCP tools the server exposes
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":{}}'

# Call a tool (here: list sites)
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":2,"method":"tools/call","params":{"name":"sites_list","arguments":{}}}'

For the tool reference, see the connect guide. For the HTTP API, see the API reference.

FAQ

Do I need an API key?

No. You sign in through your browser (OAuth) when you add the connector; there's no key to paste. An account API key is only needed if you call the HTTP API directly from a script.

Does this work with Cursor, Zed, and other MCP clients?

Yes. Any MCP-capable client uses the same endpoint, https://app.staticowl.com/api/mcp, and the same browser sign-in. Add it as a custom or remote connector and sign in when prompted. See the connect guide for per-client steps.

Is StaticOwl built for MCP?

Yes. The MCP tools map to the same operations the web app uses, so an assistant can do the work you do in the admin UI. There is no separate "AI features" tier to switch on — the tools reach the product directly.

Where can I see the live tool catalog?

Read the human-friendly version in the connect guide, or call tools/list on https://app.staticowl.com/api/mcp.