Connect Profound CMS to your AI client

Profound CMS provides a remote MCP server that lets compatible AI clients discover, create, update, publish, and manage CMS content.

MCP endpoint:

http://107.21.107.99:8081/mcp

For production, use the HTTPS version of your configured MCP URL whenever available.

Authentication

Profound CMS MCP uses WorkOS OAuth.

To connect:

1. Create a Profound CMS account.
2. Confirm that your account belongs to the correct organization.
3. Add the MCP server to your AI client.
4. Complete the browser-based login when prompted.

You do not need to copy an API key into your AI client. After login, the client receives a short-lived access token and refreshes it automatically.

Your CMS role controls access:

• Members can read CMS content.
• Editors and administrators can create, update, and publish content.

Claude Code

Run:

claude mcp add --transport http Profound http://107.21.107.99:8081/mcp

Then start Claude Code and complete the browser authentication flow.

Verify the connection:

claude mcp list

Codex CLI

Run:

codex mcp add Profound --url http://107.21.107.99:8081/mcp

Codex will request authentication when the server is first used.

You can verify the connection with:

codex mcp list

OpenCode

Add the following to:

~/.config/opencode/opencode.json

{
  "mcp": {
    "profound": {
      "type": "remote",
      "url": "http://107.21.107.99:8081/mcp",
      "enabled": true,
      "oauth": {}
    }
  }
}

Then authenticate:

opencode mcp auth profound

Verify the connection:

opencode mcp list

The server should appear as connected through OAuth.

Cursor, Windsurf, and other MCP clients

Most MCP-compatible clients support the standard remote HTTP configuration:

{
  "mcpServers": {
    "profound": {
      "url": "http://107.21.107.99:8081/mcp"
    }
  }
}

In Cursor, Windsurf, Claude Desktop, or another MCP client:

1. Open the MCP or integrations settings.
2. Add a remote HTTP MCP server.
3. Use the Profound MCP URL.
4. Enable OAuth authentication if the client provides an OAuth option.
5. Complete the Profound CMS login in your browser.

The client must support Streamable HTTP MCP and OAuth. Clients that only support local servers or static API keys cannot authenticate directly with this server.

Start every session with discovery

After connecting, ask your AI client to discover the organizations and websites available to you:

Use the Profound MCP server only.

First call list_my_organizations.
Then call list_organizations.
Use the organization ID returned by list_organizations to call list_websites.

Show the organization names, website names, and website IDs in a table.

All CMS operations require a website_id.

Available tools

The MCP server currently provides 35 CMS tools.

Organizations and websites

• list_my_organizations
• list_organizations
• list_websites

Pages

• create_page
• update_page
• delete_page
• get_page
• list_pages

Route bindings

• create_route_binding
• update_route_binding
• delete_route_binding
• get_route_binding
• list_route_bindings

Route bindings connect template pages to specific content or parameter values.

Components

• create_component
• update_component
• delete_component
• list_components

Components define reusable content types and their fields.

Blocks

• create_block
• update_block
• delete_block
• get_block
• list_blocks
• publish_block

Blocks are content instances placed on pages.

Dynamic fields and Template Builder expressions

• set_block_field_expression
• set_block_field_expressions
• list_block_field_expressions
• delete_block_field_expression

These tools manage dynamic fx expressions that calculate field values at render time.

Documents and variants

• create_document
• update_document
• delete_document
• get_document
• list_documents

Documents are reusable content entries, also called variants. list_documents returns metadata; use get_document to retrieve the full content.

Translations

• list_document_translations
• upsert_document_translation
• delete_document_translation

Translations should be stored as locale rows in a single document rather than creating a separate document for each language.

Typical CMS workflow

A complete content workflow usually looks like this:

1. Discover organizations and websites.
2. Inspect existing components, pages, blocks, and documents.
3. Create or update the required content.
4. Use expected_version when updating blocks, components, or documents.
5. Publish blocks or documents.
6. Set the page state to Live.
7. Verify the published content.

A page is publicly visible only when it is live and its content has been published.

Example prompts

Create a page:

Using Profound CMS, create a page at /pricing for website <website_id>.
Create the required blocks, publish them, and set the page to Live.

Update existing content:

Find the homepage for website <website_id>.
Read its current blocks, update the hero headline, and publish the change.

Create localized content:

For document <document_id>, add French and German translations.
Use the existing document and create translation rows instead of creating duplicate documents.

Use dynamic content:

For the hero block on the template page, make the headline pull from the route-bound document.
Use a block field expression rather than putting the formula in draft_content.

End-to-end content workflow

Profound CMS MCP can be combined with other MCP servers to support a complete workflow:

For example:

Figma MCP + Profound CMS MCP

can connect design discovery, content creation, CMS authoring, localization, and publishing into a single AI-assisted workflow.