Royally

io.royallyPublished by royally.ioOfficial publisherv0.0.898Updated Nov 1, 2026

Run every WordPress site you manage from your AI agent, with approvals, receipts and undo.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an AI assistant operate the WordPress sites you manage, with approvals, receipts and undo.

What you can do
  • Manage WordPress sites you administer from an AI agent
  • Run site operations across multiple WordPress installations
  • Require approvals before changes are carried out
  • Produce receipts of what was done and support undo
  • No individual tools are listed in the supplied manifest, so the exact command set is not documented here.
When to use it
Useful if you maintain one or more WordPress sites and want an assistant to carry out site work while keeping an approval step and a way to reverse changes.
Requirements
A remote MCP endpoint at app.royally.io over streamable HTTP. OAuth sign-in is required; no environment variables or headers are declared. A Royally account with the WordPress sites you manage connected is implied.
Before you install
The server can change live WordPress sites, so review the approval step and confirm what undo covers before relying on it. OAuth grants access to your account and connected sites; grant only to clients you trust. No tool list is published, so verify the scope of actions after connecting.

Installation

In SourceWeft

  1. Open Royally in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.royally%2Froyally/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "royally": {
      "type": "http",
      "url": "https://app.royally.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.0.898LatestNov 1, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.