Integration · MCP

StaticOwl in Cursor

Connect guide · Claude Code

What this gives you: the StaticOwl CMS wired into Cursor as an MCP server. Cursor's agent can list your sites, design content types, create and edit pages, manage releases, and trigger builds — 334 tools across 12 toolsets — without leaving your editor.

Add the connector

Cursor reads MCP servers from ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project. Add StaticOwl as a remote server with just the URL — no header:

{
  "mcpServers": {
    "staticowl": {
      "url": "https://app.staticowl.com/api/mcp"
    }
  }
}

Restart Cursor (or enable the server under Settings → MCP). Cursor opens a browser window to sign you in. Once sign-in finishes, the StaticOwl tools appear in the MCP list. There is no key to copy or paste.

To confirm the connection, start a chat and ask it to list your sites.

Choose your toolset

StaticOwl exposes 334 tools across 12 toolsets — sites; content; content types; templates & themes; media; SEO; internal links; builds & releases; domains & redirects; forms & integrations; authoring; and access & workflow. When you add the connector you pick a preset: core (a tight starter set), recommended (the default, day-to-day tools), or all (the full 334). Most people want recommended.

Use it

Ask Cursor's agent to work on your site — it inspects the tool list and picks the right calls:

Using the StaticOwl MCP, list my sites, then show the content types and a few sample pages.

Other things to try:

With more than one site, name the one you mean or set a default with the sites_set_default tool.

Safe by design

An assistant works through the same steps you do. Edits start as drafts. Content goes live only when it is published and the site is built. Every change keeps history, and a build can be rolled back. You decide what gets published.

See also

Questions? support@staticowl.com.