Shilpi MCP server
Adds WooCommerce-specific tools when the WooCommerce Kit plugin is active; the integration explicitly does not expose customers, orders, addresses, or payment data.
Allows agents to build and edit a WordPress site running the Shilpi theme, with tools for managing pages, posts, templates, menus, taxonomies, SEO, media, design tokens, global CSS/JS, PHP snippets, JavaScript files, fonts, and site settings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Shilpi MCP serverUpdate the homepage hero heading and change the button color to match our brand."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: sitepilot-mcp
Endpoints
The server runs on your own site. Replace example.com with your domain.
Purpose | URL |
Streamable HTTP, OAuth |
|
Streamable HTTP, application password |
|
OAuth protected-resource metadata |
|
Site summary for agents |
|
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
Tool | What it does |
| Site identity, versions, inventory, breakpoints, limits, template routing |
| List pages, posts and templates with ids, slugs and permalinks |
| Read one document: body HTML, page CSS, page JS, header and footer |
| Create or update a page, post or template, idempotent by slug |
| Set a document's page CSS and JavaScript |
| Remove a document |
| Import one static HTML file as a Shilpi document |
| Import a folder of static HTML: templates, CSS, images and menu |
Design system
Tool | What it does |
| List and upsert design tokens, with per-breakpoint values |
| List and manage global CSS classes and their states |
| Read global CSS and JS, and the default header, footer and front page |
| Write those global settings |
Structure and content
Tool | What it does |
| Create and order navigation menus, assign them to locations |
| Manage categories, tags and custom taxonomies |
| Read title, description, canonical, robots and social fields |
| Write them through whichever SEO plugin the site runs |
| Sideload an image into the media library, idempotent by source URL |
| Search the installed icon libraries |
| Add and remove icon libraries |
Code and assets
Tool | What it does |
| List Code Hub snippets with their enabled and error state |
| Read one snippet and its content hash |
| Create or update a snippet, syntax-checked, hash-guarded |
| Enable or disable a snippet, test-run before enabling |
| Remove a snippet |
| List managed JavaScript files |
| Upload a trusted library or bundle |
| Set enabled state, load priority and jQuery dependency |
| List project JSON and asset files |
| Upload generated JSON, returns a same-origin URL |
| Remove a project or script file |
| Activate a web-app manifest |
| List self-hosted font faces |
| Upload a WOFF2, WOFF, TTF or OTF face and register it |
| Remove a font face |
Agent instructions
Tool | What it does |
| Load a Markdown skill: |
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/.
This server cannot be deployed
Maintenance
Related MCP Connectors
Secure MCP Server for WordPress connects AI assistants and agents to WordPress with secure, controlled access. It lets AI interact with WordPress through MCP while helping organizations manage access, enforce policies, protect non-human identities (NHI), and require human approval for sensitive actions. Use it to securely connect tools such as ChatGPT, Claude, and Cursor with WordPress. Marketplace Link: https://wordpress.org/plugins/miniorange-secure-mcp-server/ Official website: https://plugins.miniorange.com/mcp-server-ai-policy-enforcement-wordpress ChatGpt Marketplace: https://chatgpt.com/plugins/plugin_asdk_app_6a312802286c8191bad0a7278a4e53ef Claude Marketplace: https://claude.ai/directory/miniorange-mcp-for-wordpress Cursor Marketplace: https://cursor.com/marketplace/miniorange
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Connect AI agents to Filepad workspaces through OAuth MCP.
Agent-first web hosting: deploy sites, apps, databases and domains over MCP.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to securely manage multiple self-hosted WordPress sites, including content editing, theme management, and maintenance operations with fine-grained permission controls.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect to WordPress sites running the SitePilot plugin by handling local transport, login, and credential management while letting WordPress enforce policies and expose its live tool list.11 npmApache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables browser-based AI agents to interact with a WordPress site through WebMCP-registered tools, allowing them to read, search, navigate, and optionally create or modify content, taxonomies, comments, and user data via the WordPress REST API.-
- FlicenseNot gradedqualityBmaintenanceConnects MCP-capable agents to an authenticated ELEMS account, enabling website creation and inventory management, page and element editing, media and template handling, structured content authoring, draft previews, and explicit publishing.-