=== Pielyt ===
Contributors: pielyt
Tags: ai, agent, mcp, automation, api
Requires at least: 6.9
Tested up to: 7.1
Requires PHP: 7.4
Stable tag: 0.1.18
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Manage WordPress sites, teammates and AI agents from one Pielyt account — no API keys, app passwords or per-site teammate accounts.

== Description ==

Pielyt makes managing WordPress with AI agents simple.

Install the plugin on each WordPress site, click **Connect**, and manage your sites, teammates and agents together from Pielyt. Claude, ChatGPT and other MCP-compatible assistants can then work with the sites you give them access to — without a separate MCP adapter, without copying API keys around, and without creating a WordPress account for every teammate on every site.

**One Pielyt account is enough for each teammate to work across every site and agent they are allowed to use.** Instead of provisioning the same person separately across every WordPress install, you give them the right access in Pielyt once.

There are no application passwords to generate, no API keys to paste into clients, and no long-lived credentials for your team to keep track of.

For one site, you can connect an unlimited number of MCP-compatible agents for free.

= One place for your sites, people and agents =

Pielyt is designed for people who work across more than one WordPress site — especially agencies, teams and anyone using several AI assistants.

* **Connect each site once.** Install Pielyt, choose what the site allows, and click **Connect this site**.
* **Manage teammates centrally.** Give each person the right access in Pielyt instead of creating and maintaining a separate WordPress account for them on every site.
* **Manage agents centrally.** Decide which agents can reach which sites and what level of access they should have from the same place.
* **Use the MCP clients you already use.** Pielyt is the connection layer. You do not need to install or configure a separate MCP adapter for every site, person or agent combination.

That means adding a new teammate or a new agent does not turn into a credential-management project across a fleet of WordPress sites.

= No API keys, application passwords or credential copying =

Connecting a site is a signed handshake started by an administrator inside wp-admin. There is no API key box and no token box on the plugin's settings screen, and there is nothing to copy from one service into another.

Your Pielyt account itself uses magic link email passcodes instead of a password. Team access is managed in Pielyt, rather than by handing everyone credentials for each individual WordPress site.

= Simple access management, enforced by each WordPress site =

You decide what each connected site allows, and give every agent as much or as little of it as its job needs — an agent kept to a single task, or a generalist working across everything the site allows.

Those limits are held in both places: by Pielyt when it passes an instruction on, and by the plugin on the site before any work runs there.

Agents work through WordPress users created specifically for agent activity, each carrying the access you chose for it. Changes appear in WordPress under a named user, and WordPress checks capabilities object by object before it makes one.

Reading works two ways. The first is through WordPress. The second is a direct question the plugin can answer about this site's own public index — an id, a title, a slug, a status, a type, an author, a date, and no content of any kind. That index holds what a visitor could already find without logging in, and nothing else, whichever agent asks. The FAQ says what it reaches.

After a site is connected, Pielyt can ask it to create one of those agent users, or withdraw its access again. The account stays in WordPress, holding nothing.

= Who it is for =

* **Agencies and teams** managing several WordPress sites who want one place to manage site access, teammates and agents instead of provisioning everyone separately on every site.
* **People using multiple AI assistants** who want Claude, ChatGPT and other MCP-compatible tools to reach the same WordPress sites without maintaining separate adapters and credentials for every combination.
* **Writers and editors** who want drafting, rewriting and publishing of posts and pages to happen from the assistant they already use and land as ordinary WordPress revisions.
* **Site owners** who want AI access without handing out administrator logins or application passwords.

= Your site stays in control =

Two rules sit underneath the rest of the design.

**Nothing can touch this site until you connect it.** A fresh install has no keys, no account association and no address it answers to. Connecting is started by an administrator inside wp-admin, and until then every instruction is refused.

**This site overrules the service.** Every local limit is checked on this site after an instruction has been verified and before any work runs. Turning something off is not a request for the service to behave differently; it is the WordPress site refusing the operation itself.

= Turn it down, or turn it off =

Three checkboxes on the settings screen let you narrow access immediately. They are stored on this site and checked on every instruction an agent sends, before it runs here. None of the three is on when you install the plugin; tick a box and the refusal starts at once.

* **Read only.** Refuses every change an agent asks for, while leaving reading in place.
* **Media library.** Stops an agent uploading, replacing, removing or reading files, and stops it listing what the library holds. It can still work with posts; it simply cannot work with media.
* **Comments.** Stops an agent reading, replying to, approving or deleting comments.

**Disconnecting is one button.** The site deletes the keys it used to check the service's instructions. The change takes effect immediately and does not require the service to agree.

The service is told what the switches are set to so it can explain why an operation was refused.

= Activity you can audit from WordPress =

Every instruction the plugin carries out, and every one it refuses, is written to a log in this site's own database when it happens — what ran, which user it ran as, and, when the answer was no, why the site refused it.

The log is under **Pielyt → Activity**. Because it is kept on the WordPress site rather than only at the service, it stays with you when you disconnect. The last 300 instructions carried out and the last 100 refused are kept, counted separately so a run of refusals cannot push real work out of the record. Uninstalling the plugin deletes the log.

Because every change an agent makes is made by a named WordPress user, it also appears in ordinary WordPress history such as post revisions, the media library and comment authors.

= Connect now, expand when you need to =

For one site, Pielyt is free and can connect that site to as many MCP-compatible agents as you like.

For teams and larger setups, your Pielyt account is where sites, agents, people and permission sets are managed together. That is what lets a team work across many sites without creating a separate WordPress account, API credential or MCP configuration for every person-site-agent combination.

== External services ==

This plugin is one half of a hosted service. It does not work on its own, and using it means sending data to a server we run. This section explains what is sent and when.

The service is **Pielyt**, at `https://pielyt.com`. A free Pielyt account is required. The plugin itself talks to `https://mcp.pielyt.com`.

**Nothing is sent until an administrator clicks Connect.** Until then the plugin makes no outbound request.

**Connecting starts with one signed request.** When an administrator clicks Connect, the site sends the service a signed request naming this site's address and its WordPress, PHP and plugin versions, and a one-time public key the site generates at that moment. Your browser then opens your Pielyt account, where you approve the connection.

**After you approve, the site finishes connecting.** The site exchanges the one-time code it was given, with a verifier only this site knows, for a token that expires after sixty seconds, and uses that token once to receive the identifiers of the connection and the public key the service will sign with. The site then shows you which organization and which account approved it. When the administrator confirms, the site tells the service the connection is installed; if the administrator cancels, it tells the service that instead.

**The service may later ask the site, under its own signature, which connection it holds.** The site answers with the number of the connection it holds and the state of any connection still being set up, signed with its own key.

Nothing about this site's content or its users travels in any of this.

**While connected**, the work runs in one direction: the service contacts this site; the plugin checks what arrives, does the work if it is allowed, and answers. The plugin does not call out on its own to perform that work. The one exception is that the activity screen retrieves a history log from Pielyt in addition to its own log, and that request carries this site's identifier and the period you chose.

**The site describes itself when the service asks it to, in a signed message.**

* One such message asks how the plugin is set up here: its own version, the WordPress and PHP versions, the REST namespaces and database views it can reach, each ability registered here with its description, the arguments it takes and what it says about itself, which switches are on, which keys it currently trusts and a fingerprint of each, the number of the connection it holds, and the identifier, number and state of any connection still being set up.
* Another asks for an inventory of the site: every plugin installed here with its version and whether it is active, every REST route this site publishes, the same list of abilities, and its post types and taxonomies. An inventory of installed plugins and their versions describes the software this site runs. Pielyt asks for it to know which abilities apply to this site. It goes to Pielyt and nowhere else, and only in answer to a message signed with a key this site has accepted.
* The public health route, which anyone can reach, answers that the site is alive.
* While a connection is being set up it also signs the service's check that it is talking to this site.
* Until a first connection is finished it also signs, for anyone who asks, the same answer about the connection being set up that the service gets, so the service can learn what became of it; once the site holds a key, it answers that question only to a message signed with a key it has accepted.

Nothing more.

**When an allowed request reads or changes content**, the answer to it travels through the service to the assistant that asked — the post, page or media that request named.

**When an agent adds an image to the media library**, the file reaches this site through the service too. Pielyt fetches it from the web address the agent named, or takes the bytes the agent sent, and passes it on with its size and fingerprint signed. The plugin checks both before WordPress stores the file, and does not fetch the file itself.

**When you disconnect**, the plugin deletes its verification keys, then tells the service once that this site disconnected itself, so your Pielyt account does not go on showing it as connected. That request carries this site's identifier and address and nothing else, and is signed with this site's key. Deleting the plugin sends the same request. Nothing from the service verifies here again and nothing further is sent until the site is connected once more.

* Terms of service: https://pielyt.com/terms
* Privacy policy: https://pielyt.com/privacy

== Installation ==

1. Install and activate the plugin.
2. Go to **Pielyt → Settings**.
3. Click **Connect this site**. Pielyt opens in the same window; sign in and approve.
4. Back in WordPress, check the organization named on the screen and press **Finish**.
5. From pielyt.com, sign in and go to **Agents → Connect an Agent** to add agents.
6. Manage sites, permissions, teammates, and agents from your Pielyt account.

There are no API keys, application passwords or MCP adapter credentials to copy into WordPress.

== Frequently Asked Questions ==

= Does every teammate need a WordPress account on every site? =

No. That is one of the main reasons Pielyt exists.

Install and connect Pielyt on each WordPress site once, then manage your team in Pielyt. Each teammate can be given the right access there instead of being separately provisioned as a human user across every WordPress install your team manages.

Agent activity on the site still runs through the plugin's own WordPress agent users so WordPress can enforce capabilities and keep an audit trail.

= Do I need API keys or WordPress application passwords? =

No. There are no API keys or application passwords for you to generate, copy into an MCP client, share with teammates or keep synchronized.

A WordPress administrator connects the site through a signed handshake from wp-admin. Your Pielyt account uses email passcodes rather than a password.

= Do I need a separate MCP adapter? =

No. Pielyt is the MCP connection layer between your assistants and your connected WordPress sites. Once a site is connected to Pielyt, you do not need to set up a separate adapter for every site, teammate or agent combination.

= Can I use several agents with the same site? =

Yes. A connected site can be used by multiple MCP-compatible agents, and Pielyt lets you manage which agents have access and at what level. One site can be connected to an unlimited number of agents on the free plan.

= Does it work on WordPress multisite? =

Yes, one site at a time. Install Pielyt on the network and activate it from the Plugins screen of each site you want to connect, exactly as you would on a single site.

What it does not do is **Network Activate**. Pielyt keeps its settings, its agent roles and its own records in each site's own tables, so activating it for a whole network would set up one site and leave the rest unable to run anything, and removing it again would leave rows behind on all of them. It refuses a network activation and says so, rather than doing that quietly.

One caveat if you run it on several sites of one network: WordPress runs a plugin's uninstall once for the whole network, so deleting Pielyt clears its data from the site the uninstall happens to run in and leaves the others' rows in place. Disconnect each site first and the part that matters is gone regardless — a disconnected site has deleted the keys it used to check Pielyt's instructions, so nothing from Pielyt can run there again.

= Can an agent install a plugin, edit a theme, or change my settings? =

No. The plugin refuses instructions aimed at the site's own options, templates and Site Editor styles, and at the REST interfaces for installing plugins, switching themes and administering user accounts. The accounts Pielyt works through do not hold permission to do any of it either.

= Can an agent read my customers' orders? =

Not in this version. This version of the plugin refuses every request that reaches WooCommerce orders, customers, subscriptions, refunds or sales reports, reads included. It also refuses any other WooCommerce request that is not about the product catalog. The accounts Pielyt works through do not hold permission to change an order or a customer. The plugin's own index read cannot return an order: it leaves order rows out of every index read, and it declares no column for a total, an address or an email.

A later version may add a switch that lets an agent work with orders. You would control it on your site, and it would be off until you turn it on. This version has no such setting.

Products and product pages are the shop's own content, and this restriction does not cover them. Product reviews are refused, because they carry reviewers' names and email addresses.

= Can I keep it away from my media library, or my comments? =

Yes, with one checkbox for each. **Media library** stops an agent uploading, replacing, removing or reading files, and stops it listing what the library holds; the agent can still work with posts. **Comments** stops it reading, replying to, approving or deleting comments. Neither is on when you install the plugin, and both are checked on this site before any work runs here.

= Can an agent delete my posts, my files or my comments? =

It can move things to the Trash, and it can never delete anything for good. The plugin refuses every request to delete permanently before WordPress sees it.

The same holds while an agent runs an ability another plugin registered: the plugin cancels any permanent deletion of a post, page, media item, comment or term made through WordPress's own functions. An ability is that other plugin's own code, so one that writes to the database directly is beyond what any plugin can stop. Pielyt lets an agent run an ability it has not reviewed only under its Administrator role.

An agent with publishing access can trash any post or page and take a published one back to draft; an agent with editing access can do neither. What is trashed this way stays in **Posts → Trash** or **Pages → Trash** until somebody empties it, and comes back as a draft. A comment an agent removes goes to **Comments → Trash** the same way. With the **Media library** switch off, an agent that may edit an attachment can trash that too, and WordPress keeps no Trash view for media, so the item simply leaves the library.

**Read only** refuses all of it.

= What can an agent change, and what is out of reach? =

Posts and pages, and what hangs off them. An agent with publishing access can write, edit, publish, unpublish and trash any post or page, attach media, create and rename categories and tags, and read, reply to, approve and trash the comments on the posts it can edit. An agent with editing access can write posts and pages and edit any of them, published ones and other people's included, attach media and create and rename categories and tags, and cannot publish, unpublish, schedule or trash anything. An agent with reading access sees what a visitor could see: published content only. On a site running Yoast SEO, Rank Math or SEOPress, an agent that may edit a post or page can also set its SEO title, meta description, focus keyphrase, canonical URL (an address on this site only), noindex and nofollow, Open Graph title, description and image, and with Yoast SEO its schema page and article type. These are written to that SEO plugin's own fields and nowhere else. On a site running the Redirection plugin, an agent with publishing access can list, add, change and delete plain 301 redirects, and reach nothing else of Redirection: not its settings, logs, imports or exports. A redirect it deletes is gone, since Redirection keeps no trash.

**Pages include the ones you may not think of as content.** Your terms, your refund policy, your contact page and, on most sites, your front page are ordinary pages to WordPress, so a publishing agent can rewrite, unpublish or trash any of them. Your privacy policy is the one exception, and it is WordPress's doing rather than ours: once a page is chosen under **Settings → Privacy**, core requires a site-owner permission to edit or trash it, and no agent has one. An agent with editing access can rewrite a published page too, though not unpublish or trash it. If that is wider than you want, give the agent reading access.

**Out of reach, for every role the plugin creates:** deleting anything for good (posts, pages, files, comments, categories and tags), and settings, plugins, themes, user accounts and the Site Editor.

One thing to know if you run other plugins: WordPress lets a plugin register content of its own on the same interfaces posts and pages use, under the same permissions. An agent that may write posts or pages may reach that content too.

= What can an agent read? =

What the site would show a signed-in user holding that role, through WordPress's own interfaces — and, separately, this site's own public index.

That index answers the question a visitor's browser answers: it lists what anybody could already find on your site without logging in, and nothing else. Published posts and pages, whatever a plugin publishes on the same interfaces and marks as public — products, for instance — and media, apart from anything attached to a post that is not itself published. Not drafts, pending or scheduled posts, not private posts, nothing in the Trash, no revisions, and none of the content plugins keep to themselves: menu items, block templates, reusable blocks, font files, coupon codes, form entries. Comments are the approved ones on those same posts; anything held for moderation or marked as spam is not there, and neither are the comments on a password-protected post.

That floor is the same for every agent, including a publishing one. An agent that needs its own drafts reaches them the other way, through WordPress's interfaces, where WordPress checks its permission one item at a time.

WordPress decides what counts as public here, not us. The index reads this site's own register of which content types and statuses visitors can see, so a plugin you install tomorrow is included or left out by the same flag that decides whether its content appears on your site at all — nobody has to add it to a list here first.

It is also a fixed list of columns: for a post, its id, title, slug, status, type, author and date; for a comment, its id, the post it sits on, that it is approved, and the date. No post content, no comment text, no email address, no IP address, no password.

One caveat, because it is the one place this differs from your site's own front page: if a plugin hides a *published* post from visitors — a membership paywall, say — that post's title and link can still appear in this index. The index reads WordPress's register of what is public; it does not run your theme's queries.

The **Comments** switch stops the comment half of it. **Read only** does not stop any of it: reading is what read-only leaves in place.

= Can an agent act as me? =

No. Agents act as users the plugin creates, never as you, and every change they make goes through WordPress under the role you chose. If a human account is ever registered under one of those names it inherits nothing: the plugin acts only as users it created itself, and refuses to act as any other.

= What happens when I disconnect? =

The plugin deletes the keys it used to check the service's instructions, so nothing from the service verifies here again. It is immediate and does not require the service to agree.

Posts, pages and files an agent already created stay exactly as they are. The agent user accounts stay too, but lose every permission the plugin gave them. Nothing is taken off an account the plugin did not create, so if you added an agent role to your own account to see what an agent sees, your own permissions are left alone.

= Can I stop everything without disconnecting? =

Yes. **Read only** on the settings screen refuses every change an agent asks for while leaving reading in place. Switching it back is one click.

= What does the site send, and when? =

See **External services** above. In short: nothing before you connect, one signed handshake when you do, and after that the service comes to this site rather than the other way around — except when you open the activity screen, which asks the service for this site's own service-side activity record, and when you disconnect, which tells the service once.

Pielyt can also ask this site, in a signed message, to describe itself: how the plugin is set up, and an inventory of the plugins installed here with their versions, the REST routes this site publishes, and its post types and taxonomies. **External services** lists what that includes.

When an allowed request reads content, the answer to that request is sent through the service to the assistant that asked. The site's switches, and the role the agent holds, decide which requests are answered and therefore which content can be sent.

= Do I need a Pielyt account? =

Yes. Pielyt is the hosted connection and management layer, so connecting requires an account at pielyt.com.

= Can I run my own MCP gateway? =

Yes, but then you have to manage your own credentials, the MCP adapter, and other setup. Pielyt exists to abstract that away.

= Where do I see what it has done? =

Go to **Pielyt → Activity**.

The top of that screen is this site's own record: the plugin writes a line there as it carries out or refuses each instruction, in this site's database, with no help from the service. It works on a site that has never been connected, on a site that has disconnected, and on a site that cannot currently reach Pielyt. The last 300 instructions carried out here and the last 100 refused are kept separately.

Beneath it, on a connected site, is what your Pielyt account has recorded about this site, which is the fuller history and the one that can include context about other people and other sites. The two are shown separately because they are different records.

Every change an agent makes is also made by a named WordPress user, so it appears in the ordinary places such as post revisions, the media library and comment authors. The settings screen also shows when the site was last used.

= Does the activity log store my content or personal data? =

No. It stores what kind of operation ran, what it named, which WordPress user it ran as, whether it was carried out or refused, and the plugin's own reason code for a refusal. It does not store arguments, request bodies, results, post content, IP addresses, or any name or address WordPress does not already hold for that user.

== Screenshots ==

1. Connect a WordPress site to Pielyt in one click from the plugin settings.
2. Pielyt activity, showing work carried out and requests refused.
3. The same site at pielyt.com, showing when it was connected, when it was last checked, and one button to disconnect it.
4. Agents at pielyt.com: each one that is connected, the site it reaches, and the role that decides what it may do.

== Changelog ==

= 0.1.18 =

* New: the same SEO fields with SEOPress: SEO title, meta description, target keywords, canonical URL, noindex and nofollow, and Open Graph title, description and image.

= 0.1.17 =

* New: with Yoast SEO or Rank Math, an agent that may edit a post or page can read and set its focus keyphrase, canonical URL, noindex and nofollow, Open Graph title, description and image, and with Yoast SEO its schema page and article type, beside the SEO title and meta description. A canonical must be an address on this site. Every value is checked by the plugin before the SEO plugin's own field is written.

= 0.1.16 =

* New: a read-only list, for an agent with administrator access, of what is hooked into every page's head and footer: each callback on wp_head, wp_body_open, wp_footer and wp_enqueue_scripts with the plugin, must-use plugin or theme its code is in, and the scripts registered outside WordPress with where each is served from. No file path leaves the site, nothing is run, and nothing is removed; removal stays in wp-admin. At `pielyt-audit/v1/hooks`.

= 0.1.15 =

* New: an agent with publishing access can credit a post or page to another author. Only a member of this site who can edit posts is accepted; an agent account, a reader or a user of another site on a network is refused. Users are never created or changed.
* New: a read-only author list (id, display name and slug of the members who can edit posts) for those agents, at `pielyt-authors/v1/authors`.

= 0.1.14 =

* New: on a site running Redirection, an agent with publishing access can list, add, change and delete plain 301 redirects. Nothing else of Redirection is reachable.
* Changed: when an ability an agent calls tries to permanently delete a comment or a term, the call is still refused, and now the agent's database writes stop for the rest of that call instead of an exception unwinding WordPress's hooks.
* Changed: Pielyt refuses agent abilities on a site whose database layer skips WordPress's query filter, and says so on its settings screen.
* Updated: bundled jetpack-autoloader 6.0.3 and polyfill-intl-normalizer 1.43.0.

= 0.1.0 =

* First release.

== Upgrade Notice ==

= 0.1.18 =
Adds SEOPress to the SEO plugins editing agents can work through.

= 0.1.17 =
Lets editing agents set the full SEO fields of a post or page through Yoast SEO or Rank Math.

= 0.1.16 =
Lets an administrator agent see which plugin or theme hooks each script into your pages.

= 0.1.15 =
Lets publishing agents set a post's author, limited to the site's existing writers.

= 0.1.14 =
Adds Redirection support for publishing agents and updates two bundled libraries.

= 0.1.0 =
First release.
