
Shilpi for WordPress
com.shilpibuilderPublished by shilpibuilder.comv1.9.4Updated Oct 24, 2026
Edit a WordPress site through scoped abilities: pages, templates, design system, SEO, shop.
Overview
Connects an AI assistant to a WordPress site running the Shilpi theme so it can build and edit pages, templates, design tokens and SEO through scoped tools.
- What you can do
- Read site info and list, read, create, update, delete or import pages, posts and templates, including page CSS and JavaScript
- List and manage design tokens, global CSS classes, and global CSS/JS with default header, footer and front page
- Manage navigation menus, categories and tags, read and write SEO fields, upload media, and search or manage icon libraries
- List, read, save, enable, test-run and delete PHP snippets, and manage script files, project files, web-app manifest and self-hosted fonts
- Load Markdown skills such as shilpi-theme or wordpress-core that describe the site's conventions
- When to use it
- Useful when you run a WordPress site on the Shilpi theme and want an agent to draft or restructure pages, apply the site's design system, or fill in SEO and menu structure without giving it server or file access.
- Requirements
- A self-hosted WordPress 6.4+ site with PHP 8.0+, HTTPS, and an active Shilpi theme with a valid licence; the server runs on your own domain. Connect via the OAuth endpoint or the application-password endpoint, and the site owner must enable the agent connection in the Shilpi dashboard.
Installation
In SourceWeft
- Open Shilpi for WordPress in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
Shilpi MCP server
Connect Claude, ChatGPT or any MCP-capable agent to a WordPress site running the Shilpi theme, and let it build and edit that site through scoped abilities rather than server access.
This repository holds the public interface: the registry manifest, the tool list, the authentication guide and example client configurations. The server itself ships inside the Shilpi theme and runs on your own WordPress install, so there is no service to sign up for and no third party sits between the agent and your site.
- Product and pricing: https://shilpibuilder.com/
- Documentation: https://shilpibuilder.com/docs/
- Permission model, explained: https://shilpibuilder.com/abilities-not-access/
Why this exists
Most WordPress page builders store a layout in their own format. An agent asked to edit such a page has to learn a proprietary widget tree, guess at its invariants and hope the vendor does not change them.
Shilpi stores a page as three plain fields: body HTML, a real stylesheet, and focused JavaScript. An agent editing a Shilpi page is editing markup it already understands. What it needs from the site is not raw access but vocabulary: which global classes exist, which design variables are defined, and what the house rules are. That is what these tools provide.
Endpoints
The server runs on your own site. Replace example.com with your domain.
Both endpoints require an active licence. Without one they return 404, and no credential will authenticate. Switching the server off in Shilpi → Dashboard → Connect an AI agent removes both endpoints, which makes it a genuine kill switch rather than a setting.
Requirements
- WordPress 6.4 or newer
- PHP 8.0 or newer
- HTTPS, required for OAuth
- The Shilpi theme, active, with a valid licence
Getting connected
See docs/authentication.md for the OAuth flow and the application-password fallback, and examples/ for ready-to-paste client configuration.
Abilities
Every tool is scoped. There is no filesystem access, no SSH, and no route to
wp-config.php or to theme and plugin files. Writing PHP snippets is a
temporary permission the site owner grants at Shilpi → Security and revokes
in one click.
The list below is generated from a live install running Shilpi 1.9.4. Counts change between releases, and the WooCommerce Kit plugin adds its own tools when it is active.
Pages, posts and templates
Design system
Structure and content
Code and assets
Agent instructions
Skills are how the site tells the agent its own conventions. You can upload your own Markdown skill to add house rules, and the agent reads it before writing.
What the server cannot do
This is the part worth reading before you connect anything.
- No filesystem access. It cannot read or write theme or plugin files.
- No shell, no SSH, no
wp-config.php. - No customers, orders, addresses or payment data through the WooCommerce tools.
- Writing PHP is off by default and is a permission with an off switch, not a setting you enable and forget.
- Uploading JavaScript requires an account with
unfiltered_html.
Licence
The contents of this repository (manifest, docs and examples) are released under the MIT licence. The Shilpi theme itself is commercial software; see https://shilpibuilder.com/pricing/.
Source: README.md at commit d45320e
Tools
0Version history
1- v1.9.4LatestSep 16, 2026
Score
50% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts