Content Connectors
Surface CMS and WordPress: where a draft an agent wrote actually goes, and what each connector does with it.
Two connectors filed under Automation that are really about the same thing: where a piece of content an agent drafted ends up.
Surface CMS
"Author content types, entries, and lifecycle from MCP-aware agents and external tools."
Surface's own headless CMS, connected to this environment. Once connected, the
25 cms MCP tools can create content types, write and
publish entries and manage assets against it, so an agent can take a draft all
the way to published without a person copying text anywhere.
Connecting is different from the OAuth cards: Authenticate takes you to an in-app setup page rather than a third-party consent screen. Once connected, the card's second button reads Manage and returns you to that page.
cms is not in the default MCP connection. Load it with
?tools=cms, or ?tools=content for the CMS plus the blog review pipeline,
content analytics and AI visibility. See
Tool Bundles.
WordPress
"Create draft posts on your WordPress site."
OAuth from the Integrations screen, against WordPress.com. Read the description literally: it creates drafts, and only drafts. Surface does not publish to your site, schedule a post, or update one it wrote earlier.
What it is for: exporting a Campaign Agents artifact to WordPress so a human can review it in the editor they already use, with the post id and edit URL recorded back on the Surface artifact.
Only an environment member who can manage integrations sees Connect and Disconnect on this card. That gate is enforced server-side, so the button is hidden rather than rendered and refused.
Neither Is a Sync
Both are one-directional and event-driven: something in Surface produces content, the connector puts it somewhere. Nothing reads your existing posts back, and nothing reconciles an edit made on the other side.
Ready to Get Started?
See it on your own site, or open the app and build the first form.