Files and knowledge
WordPress.com for AI agents.
Managed auth, ready-made tools.
Draft, publish and update posts, upload media and read comments on WordPress.com sites on behalf of each of your users.
About WordPress.com
With the WordPress.com connector, your agent manages content on each user’s own WordPress.com sites. It can list and read posts, write a draft or publish a post, update or trash it, upload media and read comments, using only the tools your project allows.
WordPress.com is a hosted platform for building and running websites and blogs.
Tools
What your agent can do in WordPress.com.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own WordPress.com connection.
-
List posts
Readwordpress_com_list_postsList the posts on a site.
-
Read a post
Readwordpress_com_get_postRead a post and its details.
-
Create a post
Writewordpress_com_create_postCreate a draft or published post.
-
Update a post
Writewordpress_com_update_postChange a post's content, status or details.
-
Delete a post
Writewordpress_com_delete_postMove a post to the trash.
-
Upload media
Writewordpress_com_upload_mediaUpload an image or file to the media library.
-
List comments
Readwordpress_com_list_commentsList the comments on a site or post.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in WordPress.com, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent draft and update posts, and switch off
wordpress_com_delete_postso it can never trash one. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example posts but not media or comments. A call outside them is refused.
Get started
Connect WordPress.com
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect WordPress.com
Each end user authorizes their own WordPress.com account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own WordPress.com account, once. const connection = await agent200 .user("user_123") .connect("wordpress_com"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the WordPress.com tools
Name the user, the model and the tools. The model decides which WordPress.com tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Draft a blog post from these notes and save it as a draft", tools: ["wordpress_com"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on WordPress.com's own sign-in page. You never see or store their WordPress.com password.
-
What access is requested
The access the connection needs, such as a chosen site or all their sites, listed on WordPress.com's authorization screen. Users can remove the app later from their WordPress.com account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the WordPress.com connector and how to use it.
Connector: WordPress.com, through Agent200. In code: "wordpress_com". What it does: Draft, publish and update posts, upload media and read comments on WordPress.com sites on behalf of each of your users. Page: https://www.agent200.com/connectors/wordpress-com/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on WordPress.com's own page, through the authorization link Agent200 returns. Never ask a user for a WordPress.com password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: wordpress_com_list_posts, wordpress_com_get_post, wordpress_com_list_comments. Write tools: wordpress_com_create_post, wordpress_com_update_post, wordpress_com_delete_post, wordpress_com_upload_media. Name "wordpress_com" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/wordpress-com/framework/claude/ https://www.agent200.com/connectors/wordpress-com/framework/chatgpt/ https://www.agent200.com/connectors/wordpress-com/framework/claude-code/ https://www.agent200.com/connectors/wordpress-com/framework/muse/ https://www.agent200.com/connectors/wordpress-com/framework/grok-bot/ https://www.agent200.com/connectors/wordpress-com/framework/openai-dots/ https://www.agent200.com/connectors/wordpress-com/framework/claude-duet/ https://www.agent200.com/connectors/wordpress-com/framework/hermes-agent/ https://www.agent200.com/connectors/wordpress-com/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/wordpress-com.md
Guides
Use WordPress.com with the AI you build on.
Step-by-step setup for WordPress.com with a specific model, assistant or agent framework.
-
WordPress.com + Claude
How to connect WordPress.com to Claude
-
WordPress.com + ChatGPT
How to connect WordPress.com to ChatGPT
-
WordPress.com + Claude Code
How to connect WordPress.com to Claude Code
-
WordPress.com + Muse
How to connect WordPress.com to Muse
-
WordPress.com + Grok Bot
How to connect WordPress.com to Grok Bot
-
WordPress.com + OpenAI Dots
How to connect WordPress.com to OpenAI Dots
-
WordPress.com + Claude Duet
How to connect WordPress.com to Claude Duet
-
WordPress.com + Hermes Agent
How to connect WordPress.com to Hermes Agent
-
WordPress.com + OpenClaw
How to connect WordPress.com to OpenClaw
FAQ
WordPress.com and Agent200, answered.
Who handles the WordPress.com OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for WordPress.com.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's WordPress.com connection, never another user's. It cannot reach anything the user or WordPress.com has not authorized.
Can I limit what my agent can do in WordPress.com?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.