manifest / ai / musespark-mcp

MuseSpark MCP Bridge

MuseSpark MCP Bridge exposes your WordPress business (posts, Yoast SEO, WooCommerce products & stock, newsletter, daily reports) as standardized MCP tools, with a built-in OAuth 2.1 authorization server and a human-in-the-loop approval queue for every sensitive write action.

by Aa Ilman · github.com/joniilmanfahmi00-collab/musespark-mcp

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/joniilmanfahmi00-collab/musespark-mcp/archive/refs/heads/main.zip

No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.

Readme github.com/joniilmanfahmi00-collab/musespark-mcp ↗

MuseSpark MCP Bridge (unofficial)

Turn your WordPress + WooCommerce store into a Model Context Protocol (MCP) server — so AI agents like Meta Muse Spark can safely run your business.

What is this?

MuseSpark MCP Bridge exposes your WordPress business (posts, Yoast SEO, WooCommerce products & stock, newsletter, daily reports) as standardized MCP tools, with a built-in OAuth 2.1 authorization server and a human-in-the-loop approval queue for every sensitive write action.

WordPress dashboard with Musespark MCP Bridge Plugin and its mascott appereance

Trademark Notice: Muse, Muse Spark, and related marks are trademarks of Meta Platforms, Inc. This project is an independent community integration and is not affiliated with, endorsed by, or sponsored by Meta. All marks are used for identification and descriptive purposes only.

Features

✅ MCP spec 2025-06-18: initialize, ping, tools/*, resources/*, prompts/* over Streamable HTTP
✅ OAuth 2.1 AS embedded: RFC 9728 resource metadata, RFC 8414 discovery, RFC 7591 dynamic client registration, PKCE S256, consent screen, refresh-token rotation, revocation
✅ Legacy scoped JWT bearer support
✅ 8 business tools: content, Yoast SEO, WooCommerce, newsletter, reporting
✅ Autonomy policy engine: read_only / draft_only / require_confirmation
✅ Admin SPA (Vue 3 + TypeScript + Tailwind): tokens, approvals, logs, settings
✅ All tokens & codes stored hashed; full audit logging

Verified With

Official MCP Inspector v2.10.1 — connected over HTTPS with full OAuth flow
Meta Muse Code (Muse Spark 1.3) — live sessions creating real products and content drafts through the approval queue

Why Muse Spark 1.3?

This plugin is designed and tested specifically with Muse Spark 1.3, the latest multimodal reasoning model from Meta AI. Here's why we chose it over earlier versions (1.1, 1.2):

Key Capabilities We Leverage

Feature	Used In	Benefit
Native multimodal perception	WooCommerce GUI automation (L3)	Agent can "see" dashboards without screenshots
Visual chain of thought	Product image analysis, competitor monitoring	Reasoning about visual content (colors, layouts)
Robust tool-use protocol	All 8 MCP tools	Reliable function calling with error handling
Multi-agent orchestration	Future: Chat Agent MVP (L2 autonomy)	Coordinate between customer-service and inventory agents
MCP 2025-06-18 compliance	OAuth flow, resource discovery	Verified end-to-end with official MCP Inspector

What About 1.1 and 1.2?

Muse Spark 1.1 (released 2025): First-generation multimodal model; lacks the mature tool-use protocol and visual reasoning we need for business automation.
Muse Spark 1.2 (released early 2026): Improved tool calling but still experimental for complex multi-step workflows like OAuth consent flows and approval queues.
Muse Spark 1.3 (released April 2026): Production-ready for agentic tasks; the only version we've verified end-to-end with live Muse Code sessions.

Forward Compatibility

The plugin's MCP server is protocol-agnostic — it speaks MCP 2025-06-18, not Muse-specific APIs. This means:

If Meta releases Muse Spark 1.4, 2.0, or future models, the plugin works without changes (as long as the model supports MCP).
Other MCP clients (Claude, Cursor, custom agents) can also connect to the same WordPress server.

Verified Compatibility

✅ Muse Code (Muse Spark 1.3) — live sessions creating products via approval queue
✅ MCP Inspector v2.10.1 — full OAuth 2.1 flow over HTTPS
⏳ Claude Desktop — planned testing after OAuth hardening
⏳ Meta AI Connectors — target submission after public release

Quick Start

composer install --no-dev -o
cd admin-ui && npm install && npm run build && cd ..
wp plugin activate musespark-mcp
wp musespark generate-token --user_id=1 --scopes='*' --ttl=3600

Point any MCP client at:

https://your-site.test/wp-json/musespark-mcp/v1/mcp

…or let the client discover OAuth automatically (401 → well-known → consent).

Tools

Tool	Access	Domain
`wp_list_posts`	read	content
`wp_create_post`	write	content
`seo_set_post_meta`	write	seo
`wc_list_products`	read	woo
`wc_create_product`	write	woo
`wc_update_stock`	write	woo
`newsletter_add_subscriber`	write	newsletter
`report_daily_summary`	read	report

Security Model

Write actions obey the policy mode; require_confirmation routes them to an admin approval queue (dashboard or, soon, chat buttons)
Scopes are validated at request time and recorded per task (audit trail)
OAuth tokens/codes hashed at rest; PKCE mandatory; refresh rotation
localhost auto-registration is development-only and will be removed before the 1.0 release (see Roadmap)

Status & Roadmap

Current: private prototype (v0.2.x), unpublished. Functionally verified locally; hardening in progress before the public release:

[ ] PHPUnit + integration test harness
[ ] Rate limiting & removal of dev-only auto-registration
[ ] Chat gateway (Telegram control bot + WhatsApp Cloud API)
[ ] Autonomy levels L0–L3 per domain
[ ] wordpress.org submission package

Powered by: Muse Spark 1.3 (Meta AI) — chosen for native multimodal reasoning, robust MCP tool-use, and production-grade agentic capabilities.

License

GPL-2.0-or-later. See LICENSE.