WeblyMCP Connect

Descripción

Drafts should land on the site, not in a paste buffer.

WeblyMCP Connect is the content layer agents use on WordPress. They can list and update posts, pages and media, moderate comments, read Contact Form 7, and work with WooCommerce when that plugin is active. You decide what they may change.

This is not the chat widget. Visitor chat is WeblyAgent Connect. This plugin does not install other plugins, manage users, or call arbitrary WordPress REST routes.

What agents can do here

  • Publish and update posts, pages and media you approve
  • Read and moderate comments
  • Use WooCommerce products, orders and reviews when WooCommerce is active
  • Read Contact Form 7 forms and the submissions you already store
  • Use the cloud tools you connect in WeblySuite (calendar, mail, Jira, GitHub, Stripe and the rest of your plan). Those tools are not inside this zip.

Install it with the family

All three plugins are in the Plugin Directory.

Requirements

WeblyConnect stores the WeblyToken. Extra integration seats come from your plan. WeblySuite enforces those seats on the service. This zip does not hide PHP files behind a license key.

WeblySuite ecosystem

Product page: https://suite.weblyarts.com/weblymcp-connect/

WeblySuite: https://suite.weblyarts.com/

Terms of Service: https://suite.weblyarts.com/terms-of-service/

Terms of Service (EN): https://suite.weblyarts.com/terms-of-service-en/

Privacy Policy: https://weblyarts.com/en/privacy

Bundled libraries

Runtime PHP libraries live in vendor/ (including mcp/sdk). They are shipped in the plugin zip. Site owners do not run Composer.

vendor/phpstan/phpdoc-parser is a runtime dependency of `phpdocumentor/reflection-docblock` used by `mcp/sdk`. It is not the PHPStan analyser.

External services

This plugin talks to WeblyArts and, only after you connect them, to Google.

WeblySuite / WeblyMCP

Used to run AI agents and inbound MCP against this site after you connect a WeblyToken in WeblyConnect.

Data sent: tool calls you enable, site name, plan snapshot, OAuth connection status for tools you choose to link. Sent when you connect the account and when an agent uses a granted handler.

Service: https://suite.weblyarts.com/

Terms: https://suite.weblyarts.com/terms-of-service-en/

Privacy: https://weblyarts.com/en/privacy

Google (Calendar OAuth)

Used only if you connect Google Calendar from this plugin (OAuth authorization code exchange).

Data sent: OAuth client id, client secret, redirect URI, and the authorization code Google returns. Sent when you complete the Connect Google Calendar flow.

Service: Google Identity / Google Calendar

Terms: https://policies.google.com/terms

Privacy: https://policies.google.com/privacy

Other cloud tools (Gmail, Jira, GitHub, Stripe, and similar) are connected through WeblySuite, not directly from this zip. Their terms apply on the WeblySuite console when you link them.

Privacy

After you connect a tenant token in WeblyConnect, this site may send to WeblyArts:

  • Tool calls you enable (MCP handlers and granted REST routes)
  • Site name and billing snapshot requests (via WeblySuite)
  • OAuth connection status for cloud tools you choose to link

See https://weblyarts.com/en/privacy and https://suite.weblyarts.com/terms-of-service-en/

Instalación

  1. Install and activate WeblyConnect.
  2. Upload the weblymcp-connect folder to /wp-content/plugins/ or install the zip.
  3. Activate WeblyMCP Connect.
  4. Connect a WeblyToken from WeblyConnect, then open WeblyMCP Connect in wp-admin.
  5. Enable the integrations and handlers you accept on this site.

FAQ

Does it work without WeblyConnect?

No. WordPress will refuse to activate it (Requires Plugins: weblyconnect).

Is WeblyAgent Connect required?

No. Chat is optional. This plugin exposes site tools to WeblySuite. The visitor widget is a separate listing.

Do I need a paid WeblySuite account?

The plugin code is free and GPL. Cloud tools and extra integration seats run on WeblySuite (trial or paid). If a request is over your plan, the service returns an error.

Does the plugin phone home before I connect?

No. Until you connect a WeblySuite account in WeblyConnect, this plugin does not call WeblyArts tool APIs.

Where do updates come from?

When hosted on WordPress.org, plugin updates come from the Plugin Directory only.

Can agents administer this WordPress site?

No. Agents can work with content you grant (posts, media, comments, forms, store data). They cannot install plugins, manage users, or call arbitrary WordPress REST routes.

Reseñas

No hay reseñas para este plugin.

Colaboradores y desarrolladores

"WeblyMCP Connect" es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

Traduce "WeblyMCP Connect" a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

0.4.28

  • WordPress.org directory release.

0.4.27

  • The dossier bearer authenticates only this plugin’s MCP routes. It does not log in to WordPress admin or core REST.
  • Activation no longer deletes a user named webly-bridge.
  • Post list returns only posts the current user can read.
  • Block HTML is saved through the WordPress post allowlist. Script tags are removed.

0.4.26

  • Update an attachment title, caption, description, or alt text with wp_update_media. Featured image stays featured_media on the post.

0.4.25

  • Read Bearer from PHP-FPM HTTP_AUTHORIZATION, not only getallheaders().

0.4.24

  • Inbound MCP uses the WordPress Application Passwords hook (determine_current_user) and wp_getallheaders(). A Bearer-only cloud call no longer stays anonymous until REST_REQUEST is set.

0.4.23

  • Remove remote administration from the plugin: no plugin, user, or arbitrary REST handlers. Leftover webly-bridge accounts from older builds are deleted once on upgrade.

0.4.22

  • Inbound MCP is contents and data only. No bridge user. No remote plugin, user, or arbitrary REST tools.

0.4.21

  • Inbound MCP: the editor bridge user is created only when an administrator connects a dossier and confirms administrative delegation. Bearer auth never creates users.

0.4.20

  • WordPress 7.0: post meta get/list use the mapped per-key cap. read_post_meta is no longer mapped in core.

0.4.19

  • WordPress.org T2: drop vendor CLI binaries from the zip. Post meta tools use read/edit/add_post_meta per key.

0.4.17

  • WordPress.org T1: enqueue overlay JS, drop user create/update tools, document Google and WeblySuite, upgrade mcp/sdk.

0.4.16

  • WordPress.org packaging: directory readme, Privacy and Terms, text domain file name.
  • Drop Composer/shell install fallback. The zip must include vendor/.
  • Plan seats for extra integrations come from WeblyConnect. No local plan table in this plugin.

0.4.15

  • Handler grants and visitor sync aligned with CTR catalog fields.

0.4.12

  • Wizard dossier: search by title or ID, alphabetical order.

0.4.11

  • MCP Server tool cards: Italian labels, grouped counts, search empty state.

0.4.10

  • MCP Server admin: grouped tool cards, search, and copyable inbound endpoint.

0.4.9

  • Clearer Google Calendar connect copy and redirect to WeblySuite instead of a missing AgentHub OAuth route.

0.4.2

  • WordPress.org packaging: GPL header, directory zip, no CDN updater.