Pielyt Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin 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
Screenshots
Connect a WordPress site to Pielyt in one click from the plugin settings.
Pielyt activity, showing work carried out and requests refused.
The same site at pielyt.com, showing when it was connected, when it was last checked, and one button to disconnect it.
Agents at pielyt.com: each one that is connected, the site it reaches, and the role that decides what it may do.

