WordPress.com + Grok Bot

How to connect WordPress.com to Grok Bot

Set up WordPress.com for Grok Bot with Agent200, then check which tools are available to your agent.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. WordPress.com tools
  7. How it works
  8. Troubleshooting

Overview

This guide connects WordPress.com to Grok Bot through Agent200's MCP server. When you finish, Grok Bot can search, read and act in WordPress.com with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Grok Bot with your Agent200 API key. Your WordPress.com account is connected through managed OAuth: you approve access once on WordPress.com's own page, and Agent200 keeps the connection working.

Connector
WordPress.com
Works with
Grok Bot ยท Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
7 tools
MCP server
https://api.agent200.com/mcp/

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • WordPress.com enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a WordPress.com account. They approve access once, on WordPress.com's own page.
  • Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.

Connect WordPress.com to Grok Bot

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers WordPress.com and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Open the custom connector form

    In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.

  3. 3

    Step 3: Fill in the server and your key

    Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header: Authorization with the value Bearer followed by your key. Leave Client ID empty, then choose Add plugin.

    Add a custom connector
    MCP: Grok Bot custom connector form
    Name:          Agent200
    Type:          Remote HTTPS
    Server URL:    https://api.agent200.com/mcp/
    HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
  4. 4

    Step 4: Attach Agent200 in a chat

    In a Bot chat, type @ and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.

  5. 5

    Step 5: Connect your WordPress.com account

    The first time you ask Grok Bot for something in WordPress.com, Agent200 returns an authorization link. Open it and approve access on WordPress.com's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.

Test your connection

Run one request to check everything is wired up.

Ask

Ask Grok Bot to list the Agent200 tools available for WordPress.com, including which are read-only.

What should come back

  • A list of the WordPress.com tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for WordPress.com and make sure its tools are enabled. Tool availability depends on your project setup.

Get your API key

Create a key in the Agent200 dashboard. It reaches WordPress.com and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect WordPress.com to Grok Bot.

Agent brief
Goal: connect WordPress.com to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/wordpress-com/framework/grok-bot/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure WordPress.com is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands.
4. The first WordPress.com request returns an authorization link if the user has not connected WordPress.com yet: show it to them and continue once they have approved access on WordPress.com's own page.
5. Check it works with this request: "Ask Grok Bot to list the Agent200 tools available for WordPress.com, including which are read-only."
   What should come back:
   - A list of the WordPress.com tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in WordPress.com, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/wordpress-com/framework/grok-bot.md

WordPress.com tools Grok Bot can call

  • 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.

How it works

  1. 01

    You ask Grok Bot

    In your own words, for something in WordPress.com.

  2. 02

    Grok Bot picks a tool

    It sees the WordPress.com tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    With your own WordPress.com connection, within the tools and scopes your project allows.

  4. 04

    Grok Bot answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's WordPress.com account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and WordPress.com enforces what its API grants.

Troubleshooting

The server cannot be saved, or shows Disabled by team admin

Your team’s connector policy blocks it. Ask the admin to allow the Agent200 server address on the Plugins & MCPs page of the Cursor dashboard.

Calls fail on a team with a network allowlist

If the admin applies the network allowlist to MCP servers, api.agent200.com must be on it.

The connector shows Needs auth, or tools return 401

Check the Authorization header is exactly Bearer, a space and a valid key, then reconnect. If the key was replaced, remove the connector and add it again.

The Bot cannot see the WordPress.com tools

Check Agent200 is enabled in your plugins, attach it with @ in the chat, and start a new chat if it was added mid-conversation.

Grok Bot shows a WordPress.com authorization link

You have not connected WordPress.com yet, or the connection needs to be approved again. Open the link, approve access on WordPress.com's own page, then ask Grok Bot again.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that WordPress.com and the tools you need are enabled in the dashboard's Connectors settings, and that you granted WordPress.com the access the task needs.

The API key was pasted into a chat or committed

Create a new key on the API keys page, replace it in Grok Bot's MCP settings, and stop using the old one. Paste the key only into Grok Bot's settings, never into a chat.

Use WordPress.com with another framework

200 OK

WordPress.com, connected to Grok Bot.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

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)