WordPress.com

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

    Read
    wordpress_com_list_posts

    List the posts on a site.

  • Read a post

    Read
    wordpress_com_get_post

    Read a post and its details.

  • Create a post

    Write
    wordpress_com_create_post

    Create a draft or published post.

  • Update a post

    Write
    wordpress_com_update_post

    Change a post's content, status or details.

  • Delete a post

    Write
    wordpress_com_delete_post

    Move a post to the trash.

  • Upload media

    Write
    wordpress_com_upload_media

    Upload an image or file to the media library.

  • List comments

    Read
    wordpress_com_list_comments

    List the comments on a site or post.

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_post so 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. 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.js
    Conceptual example
    Set 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. 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.js
    Conceptual example
    Let 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. 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.js
    Conceptual example
    Run 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.

Agent brief
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.

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.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with WordPress.com.
Your agent does the rest.

Your users connect their own WordPress.com accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)