30 days free. No credit card. Full access from the moment you connect your site.

Start free trial
AcrossAI

AcrossAI

Pricing

The complete platform

Everything your AI needs to run WordPress

Every other WordPress MCP service routes your site through their cloud. AcrossAI doesn’t. Connect Claude, ChatGPT, Grok, Gemini or Cursor straight to your own server — hundreds of ready-made actions, and you decide precisely who reaches what.

Get started →
See how it works

Runs on your own server · Bring your own AI · Any WordPress host

Works with any MCP client

Claude

ChatGPT

Cursor

Grok

Gemini

Codex

GitHub Copilot

VS Code

Claude Code

+ any MCP client

350+

Abilities on any site, day one

800+

With your plugins detected

24

Plugin integrations

0

Relays between you and your AI

What is AcrossAI?

AcrossAI is a family of WordPress plugins that add an open Abilities API and a built-in MCP server to your site. Abilities Manager supplies the actions and governs every one of them; MCP Manager serves them to any AI client; AcrossAI Pro adds one-click connectors, membership-aware access and deep plugin packs.

Set up in about a minute

Connect your AI in three steps

1

Install the plugins

Add Abilities Manager and MCP Manager from WordPress.org. They share one admin menu and one settings page, and your site starts serving abilities immediately.

2

Review each ability

See every ability exactly as the AI will — slug, input and output schema, annotations — then allow or disallow each one, and curate what each server exposes.

3

Connect your AI

Point Claude, ChatGPT, Cursor or any MCP client at your endpoint. Try the interactive Quick Connect demo before you install anything.

How it fits together

One platform, three layers

Each layer is useful on its own. Together they are what lets an assistant actually operate a WordPress site instead of just writing about one.

The capability layer

Abilities Manager

WordPress 6.9 shipped an Abilities API but almost no abilities. Abilities Manager supplies them — 350+ on a stock site, over 800 once it detects the plugins you already run — and gives you a switch for every single one.

  • 350+ abilities across 14 toolsets, no configuration
  • Browse, override and bulk-manage every one
  • Reachable over REST, with or without an AI

Explore Abilities Manager →

The connection layer

MCP Manager

A complete admin UI over the official WordPress MCP Adapter. Your site is the server — there is no relay in the middle, and no outbound HTTP request is made on your behalf.

  • Run several MCP servers, each scoped differently
  • Curate exactly which tools each one advertises
  • HTTP, STDIO and CLI, with 16 client guides built in

Explore MCP Manager →

The access layer

AcrossAI Pro

One-click connectors for the AI clients that expect to sign in, an authorisation server that runs on your own domain, and access rules that understand memberships rather than just roles.

  • Connectors for Claude, ChatGPT, Gemini, Grok and Cursor
  • Gate access by membership, not just by role
  • Deep packs for the plugins your business runs on

Explore AcrossAI Pro →

Capabilities

What your site can do, out of the box

Content

Posts, pages and any custom post type with their meta and revisions — content/create-post and its siblings. Moderate comments, manage media, categories and tags, run semantic search, and propose, review and apply internal links.

Blocks

Read and surgically edit a page’s block tree without rewriting the page. Build from patterns, generate whole sections and landing pages, and audit copy and design.

Appearance

theme.json and global styles, site-editor templates and template parts, navigation menus, widget areas, fonts, and the site title, logo and icon.

Users & roles

Create and edit users, reset passwords, create roles, and grant or revoke individual capabilities.

Configuration

Read and write any option — including values nested inside serialised arrays — change permalinks, and walk the admin menu to find which screen a setting actually lives on.

Database

Inspect schema and table sizes, audit index health and bloated autoloaded options, EXPLAIN a slow query, optimise tables, or run database/search-replace — serialisation-safe, and a dry run unless you say otherwise.

Files

Browse, read, write and delete files inside an administrator-defined allowlist. Take and extract zip backups, read and edit wp-config constants, and read the debug log — with secrets redacted.

Cron & updates

See every scheduled task and prove whether WP-Cron is firing at all. Search WordPress.org, install and update plugins, themes and core, roll back, and verify files against official checksums.

Diagnostics & cache

Site Health, maintenance mode, recent fatal errors, and un-pausing what WordPress auto-disabled. Plus transients, object cache and rewrite rules.

Governance

Control every ability on your site

Supplying the abilities is half the job. The other half is letting you see exactly what each one does — and decide, one by one, whether an AI may touch it.

Every ability, one table

A searchable, sortable, paginated list of every registered ability, filterable by source and status — so you can find content/create-post among hundreds without scrolling.

See it as the AI sees it

Open any ability to read its slug, its JSON input and output schema, and its annotations — the same description the assistant receives. No guessing what a tool will do.

Allow or disallow, site-wide

One click, saved without a page reload, and applied up to 50 at a time in bulk. A disallowed ability is unregistered outright rather than merely hidden.

Force Block, or inherit

Per ability, override what the registry says — or leave it inheriting the default. A hard block stays blocked no matter what the providing plugin declares.

Decide what MCP sees

Show or hide each ability on MCP independently of REST, set which servers carry it, and choose how it is presented — as a tool, a resource or a prompt.

Overrides that survive updates

Rewrite the readonly, destructive, idempotent and show_in_rest annotations with a Yes / No / Inherit control. Overrides live in their own table — the WordPress registry is never modified, so a plugin update never resets your decisions.

14 tools, not 350

An AI client is handed its list of tools once, when it connects, and pays for that list out of its context window in every conversation. Hand it hundreds and it drowns — most assistants degrade badly past a few dozen.

So abilities are grouped into toolsets, and a toolset is a single tool answering three actions: discover to list what it holds, info to read one ability’s parameters, and execute to run it. The same three everywhere, so an assistant learns the pattern once. Your AI sees roughly fourteen tools and reaches every ability through them, drilling in only when it needs to.

The MCP server

Your site is the MCP server

MCP Manager is a full admin UI over the official WordPress MCP Adapter. Your endpoint is a route on your own domain — /wp-json/mcp/mcp-adapter-default-server — and every request terminates there. Nothing is proxied, nothing is queued on someone else’s infrastructure.

Run more than one server

Each MCP server gets its own route, namespace and version, and can be enabled or disabled independently — a read-only server for a client, a full one for yourself.

Curate every tool

Decide exactly which toolsets a server advertises and which individual abilities are exposed through it, with filters and bulk actions across hundreds of entries.

Admin-only by default

A new server requires manage_options until you write a rule saying otherwise, and the gate fails closed. Access is then granted by user, role or capability.

Checked on every request

Access is enforced per call, not at setup. Remove someone’s access and their next request is refused — even if they still hold a working configuration on their machine.

Three ways to connect

HTTP for desktop and hosted clients, STDIO for local tools through a subprocess so no credential crosses the network, and CLI sign-in approved in your browser. Sixteen clients have step-by-step guides built in.

A log of who connected

Every CLI sign-in attempt is recorded per server — approved, successful and failed — so an unexpected connection is visible rather than silent.

Try the interactive Quick Connect demo →

AcrossAI Pro

Five AIs, one dashboard

Some AI clients expect to sign in rather than hold a password. Some sites have members, not just administrators. And some plugins are too important to reach through generic abilities.

Explore the Claude, ChatGPT, Grok, Gemini and Cursor connectors.

One-click AI Connectors

Claude, ChatGPT, Gemini, Grok and Cursor connect by signing in — no Application Password to generate, no JSON to paste, and nothing for a non-technical colleague to get wrong.

Your own OAuth server

OAuth 2.1 with PKCE, dynamic client registration, resource indicators and authorization server issuers — running on your domain, not ours. The authorisation screen is yours, and so are the tokens.

Membership-aware access

Decide who may connect an assistant based on their membership — across MemberPress, Paid Memberships Pro, WooCommerce Memberships, Restrict Content Pro, LifterLMS, WishList Member, Memberium and s2Member.

Community & learning

Run BuddyBoss from an assistant — members, profiles, groups, activity, forums, messages, media and moderation. LearnDash brings courses, lessons, quizzes, enrollment, progress, groups, certificates and reporting.

Directory & email

GeoDirectory listings, locations, fields, pricing and layout. MailerPress campaigns, contacts, lists, tags, templates and workflows — extended with segments, custom fields, webhooks and WooCommerce email templates.

Automation

An n8n endpoint lets a workflow automation platform call your abilities directly. It ships in Beta and stays switched off until you turn it on.

Integrations

The plugins you already run

Each integration registers only when that plugin is active, so nothing appears for software you do not have.

Browse the full integration directory →

Building something of your own? Third-party developers can register a toolset through a filter, without touching any AcrossAI plugin.

Safe by default

Real guardrails, not promises

  • Nothing is wide open. Every ability runs WordPress’s own capability check for the calling user, so reaching one through AcrossAI grants nobody anything they could not already do.
  • Read-only by inspection. Roughly half the catalogue is annotated read-only and only about 13% is flagged destructive — so building a look-but-don’t-touch surface is a matter of filtering, not trust.
  • Dangerous things ask first. Higher-risk operations require an explicit confirmation flag before they run, and search-and-replace is a dry run unless you deliberately say otherwise.
  • Undo an AI mistake. File-manager writes can keep a pre-image backup of every file they touch and append an entry to a changelog — what changed, when, and the context the assistant gave — both toggle-gated, and readable back through a changelog ability.
  • Files are fenced in. File access is confined to an administrator-defined allowlist, with a dangerous-extension blocklist, a double-extension check and a maximum write size on top. An empty write-allowlist means deny all writes.
  • Secrets are redacted. Database credentials and authentication salts are stripped out of file and debug-log reads, and database abilities never accept a raw table name.
  • Off means gone. An ability you disallow is unregistered outright rather than merely hidden — and overrides live in their own table, so the WordPress registry is never modified.
  • Revocable access. Connect through WordPress Application Passwords and revoke in one click, or through your own OAuth server — and access is re-checked on every request, not just at setup.
  • Your data stays home. Everything runs on your WordPress install — no telemetry, no relay, no content routed through anyone else’s cloud.
In practice

What people actually do with it

Real walkthroughs, start to finish — what was asked, what the assistant did, and what came out the other end.

See all use cases →

Frequently asked questions

What is a WordPress ability?

An ability is a self-describing operation that WordPress 6.9’s Abilities API lets a plugin register — something an AI assistant, a REST client or another plugin can discover and call. Each one carries a slug like content/create-post, a JSON schema for its input and output, and annotations saying whether it is read-only, destructive or idempotent. WordPress ships the API; almost nothing ships abilities. Abilities Manager does.

What is MCP Manager?

MCP Manager is a complete admin UI for the official WordPress MCP Adapter. The adapter provides the protocol plumbing; MCP Manager gives you the screens — create and scope multiple servers, curate which tools each advertises, set who may reach them, generate client configuration, and watch the connection log. Your endpoint lives at /wp-json/mcp/mcp-adapter-default-server on your own domain.

How do Abilities Manager and MCP Manager relate?

Abilities Manager is the capability layer; MCP Manager is the connection layer. Abilities Manager supplies the actions and governs which ones exist and what each may do. MCP Manager takes the ones you have allowed and serves them to AI clients over the Model Context Protocol. Either works alone — abilities are reachable over REST without MCP, and MCP Manager will serve abilities from any plugin — but together they are the point.

Does my content pass through your servers?

No. Your site is the MCP server, and every request terminates at your own /wp-json/ route. There is no telemetry and no relay. The OAuth authorisation server also runs on your domain rather than ours — the sign-in screen is yours, and so are the tokens.

Which AI do I use with it?

Whichever one you already have. You bring the Claude, ChatGPT, Cursor or Copilot you are already using — their free plans work too — and AcrossAI never charges for AI inference, because none of it runs here. There is no vendor lock-in and nothing to migrate if you switch assistants.

Which AI clients are supported?

Any MCP-compatible client. Sixteen have built-in setup guides — among them Claude Desktop, Claude Code, Cursor, VS Code, GitHub Copilot and Codex — which connect with a WordPress Application Password. Claude, ChatGPT, Gemini, Grok and Cursor can instead use a one-click connector, where the user simply signs in.

Is it safe to give AI access to my site?

Every ability runs WordPress’s own capability check for the calling user, so an assistant can never do something its account could not already do. On top of that, higher-risk operations require an explicit confirmation flag, file access is confined to an allowlist you define, search-and-replace is a dry run by default, and any ability can be disallowed site-wide — which unregisters it outright rather than merely hiding it.

Can I limit what one assistant is allowed to touch?

Yes, at two levels. Site-wide, you can allow or disallow any ability, Force Block it regardless of what the providing plugin declares, and override its annotations. Per-connection, you can run several MCP servers and curate exactly which toolsets and abilities each one advertises — so a read-only server for a client and a full one for yourself is a normal setup, not a workaround. Access to each server is granted by user, role, capability or membership, and re-checked on every request.

Can I use the abilities without an AI assistant?

Yes. Abilities are the capability layer, not the connection. They are registered with show_in_rest, so they are reachable over the WordPress REST API and callable by any plugin the moment you activate them — an AI client is one consumer among several.

Does it work with my hosting provider?

Yes. If you can log into your wp-admin dashboard, you’re good — shared hosting, VPS and managed WordPress all work, because everything runs inside your own WordPress install. Abilities Manager needs WordPress 6.9 or later, since the Abilities API arrived in 6.9; MCP Manager needs WordPress 7.0 or later. Both need PHP 8.1 or later.

What happens if I uninstall?

Nothing is left behind and nothing is silently destroyed. Ability overrides live in their own table and the WordPress registry is never modified, so removing AcrossAI leaves the registry exactly as it found it. Uninstall is non-destructive by default — deleting your servers and rules is something you have to ask for explicitly.

Can I add my own abilities?

Yes. The Abilities API is open, so any plugin can register typed, permissioned actions and they appear automatically. Third-party developers can also register a whole toolset of their own through a filter, without modifying any AcrossAI plugin.

Give your AI access to WordPress

Install Abilities Manager and MCP Manager, and connect your first assistant in about a minute.

Get started →
Read the docs

Runs on your own server · Bring your own AI · Any WordPress host