Integrations · Content

Connect WordPress.com to Well

Name: WordPress.com entities in Well
Creator: Well

Bring WordPress posts, pages, and comments into Well, joined to the team members who published them and any customer references they contain.

Connect WordPress.comSee what Well does

What Well pulls from WordPress.com

WordPress.com feeds post, page, comment into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke WordPress.com’s access.

From WordPress.com	In Well	Relation
Post	Workspace document	Indexes as
Page	Workspace document	Indexes as
Comment	Engagement signal	Becomes
Author	Team member	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: WordPress.com → Well

What Well does with your WordPress.com connection

Connect

Connect WordPress.com over OAuth (MCP DCR): Well registers a client through WordPress.com's OAuth Dynamic Client Registration and you approve on WordPress.com's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings post, page, and comment in from WordPress.com on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each WordPress.com entity into workspace document, engagement signal, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from WordPress.com lands in the workspace as workspace document, engagement signal, and team member you can search, chart, and automate.

Questions WordPress.com unlocks

Ask in plain language. Well answers from your connected WordPress.com connection, resolved against the rest of your stack.

Ask Well

Ask anything about your WordPress.com connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your WordPress.com connection…

Connect WordPress.com in three steps

01
Authorise WordPress.com via MCP
From Well's Connections panel, search for WordPress.com and click Connect. Well discovers WordPress.com's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on WordPress.com's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverpublic-api.wordpress.com/wpcom/v2/mcp/v1
02
Map your entities
Well's MCP client discovers post, page, comment, and author from WordPress.com that WordPress.com's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
03
Use the data
Ask questions in conversation, build records tables, or let agents act on WordPress.com records. Because WordPress.com ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical WordPress.com records happens in the background.

How WordPress.com stays secure with Well

Well connects to WordPress.com's MCP server (public-api.wordpress.com/wpcom/v2/mcp/v1) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived WordPress.com secret. Tokens are scoped to the post, page, comment, and author WordPress.com exposes and refreshed server-side. Reads only, Well cannot modify or delete WordPress.com records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestspublic-api.wordpress.com/wpcom/v2/mcp/v1

Read WordPress.com records
Resources the WordPress.com MCP server exposes, scoped by your OAuth approval.
granted
Resolve post, page, comment, and author across your stack
Match identifiers in WordPress.com against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete WordPress.com records
Not granted; WordPress.com is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store WordPress.com passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or WordPress.com’s admin panel.

Frequently asked questions about WordPress.com and Well

From Well, open Connections, find WordPress.com, and click Connect. Well discovers the OAuth metadata at public-api.wordpress.com/wpcom/v2/mcp/v1/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on WordPress.com's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in post, page, comment, and author from WordPress.com and reshapes each entity into your workspace: post becomes workspace document; page becomes workspace document. Every record arrives with the source identifier preserved, so WordPress.com stays the source of truth while Well lets you query the data alongside the rest of your stack.

Each WordPress post, page, and comment is linked to the workspace team member who published it and any customer or workflow entity referenced in the body. Ask "what did marketing publish about our enterprise tier this month" and Well returns the posts with author and customer-mention context.

Well watches for updates to posts and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right workspace document. Edits flow in incrementally; nothing is duplicated, and the WordPress.com source identifier is retained on every revision.

Well combines live WordPress.com events with periodic reconciliation reads of post, page, comment, and author. New rows appear within seconds when WordPress.com pushes them; periodic reads catch anything a push missed. The first connect backfills history from WordPress.com in the background.

Open Connections > WordPress.com in Well and click Disconnect. Well calls WordPress.com's token revocation endpoint and stops calling WordPress.com immediately on its side; provider-side propagation to WordPress.com's admin panel varies by provider. The post, page, comment, and author Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

WordPress.com records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.