MCP Integration

Status

This is on our Stage 3 roadmap. No SyncupSuite-specific MCP server exists yet. This page documents what you can do today and what's coming.

What You Can Do Today

The marketplace plugin includes mcp subcommands in both command frames that scaffold an MCP server on Cloudflare Workers:

/webplatform4sync:frame mcp    # Construction frame
/webplatform4sync:ha mcp       # Shu-Ha-Ri frame

These route to Cloudflare's built-in cloudflare:building-mcp-server-on-cloudflare skill, which scaffolds a remote MCP server with OAuth on Workers. You get a working MCP server for your own project -- it just does not have SyncupSuite-specific operations yet.

What's Planned

A remote MCP server on Cloudflare Workers with OAuth that exposes theme operations, tenant context, and token governance queries.

Planned Operations

Operation	Description	Example
themes.list	List all available themes with metadata	Returns 12 theme objects with slugs, names, cultural context
themes.getTokens	Retrieve token values for a specific theme	themes.getTokens("swiss-international", "semantic.light")
themes.getMeta	Get cultural metadata for a theme	Returns foundation story, philosophy, seed colors
themes.validateOverride	Check if a token override is allowed at a given tier	themes.validateOverride("status.error", "T1") returns { allowed: false, reason: "protected" }
tenants.resolve	Resolve a domain to its tenant context	tenants.resolve("brand.example.com") returns tenant ID, tier, status
tenants.getConfig	Get tenant configuration including active theme	Returns theme slug, allowed overrides, tier settings
governance.checkPermission	Check override permissions for a tier/path combination	governance.checkPermission("T2", "interactive.primary") returns { allowed: true }

Architecture

Claude Code / LLM client
       |
       v
MCP Server (Cloudflare Worker)
  ├── OAuth authentication
  ├── Theme operations (reads from @syncupsuite/themes)
  ├── Tenant queries (reads from Neon via Hyperdrive)
  └── Governance checks (reads PROTECTED_TOKEN_PATHS)

The server will be a standard Cloudflare Worker with the MCP protocol handler. OAuth scopes will control which operations a client can perform -- read-only theme operations will be available without tenant credentials.

Scaffolding Your Own MCP Server Now

If you need an MCP server for your project today:

/webplatform4sync:ha mcp

This gives you:

• A Cloudflare Worker with the MCP protocol handler
• OAuth setup (client registration, token exchange)
• A starter set of tools you can extend
• Deployment to your Cloudflare account

From there, you can add your own tools that query your Neon database, read your theme configuration, or expose any operation your project needs.

For the full MCP-on-Workers guide, see the Cloudflare MCP documentation.

Next Steps

• Marketplace Plugin -- the current AI-native interface
• llms.txt -- machine-readable project context
• Token Governance -- the tier rules the MCP server will enforce