Official MCP: per-tool permissions and multi-site management for agency use

[RaphaelNeuberger]

Describe the Problem

We're an IT services company (NewmountainsIT, Germany) running Elementor sites for SMB clients. We already drive Elementor from Claude Code daily through a community MCP implementation, and the official MCP announced for September is something we want to standardise on.

The blocker for production use is access granularity. An MCP client gets an agent that can create pages, change page and site settings, and publish — against a live client site. Prompt injection and tool-poisoning are documented risks in MCP setups, and one bad tool call on a client's production site is a business problem, not a technical one.

If the official MCP ships as a single all-or-nothing connection, we can only use it on staging. That removes most of its value: the sites where an agent saves us real time are the ones under maintenance contracts.

A second blocker is planning. Angie is free with a daily credit limit. Whether that limit also applies to MCP tool calls decides whether this is usable at agency volume — and there's no way to plan a rollout across client sites without knowing.

Propose a Solution

Per-tool enable/disable, per site. A settings screen listing every exposed MCP tool with a toggle, defaulting write and publish tools to off. This is the single most important item — it's what makes the difference between staging-only and production use.
Read-only mode as a first-class option. One switch that exposes only inspection tools, so an agent can audit and report on a client site without any write path.
Scoped connections. Bind a connection to a subset of capabilities (e.g. page structure only, no site settings, no plugin or file access) rather than to a WordPress user's full rights.
Multi-site management. Some way to manage MCP connections across many client sites centrally — issue, rotate and revoke access without logging into each site individually.
Transparent metering. Documented, visible limits for MCP tool calls, separate from Angie's in-editor credits.

Additional Context

Announced in the webinar on 18 August 2026 ("Generate a cinematic scroll page + Elementor MCP teaser") with a September release and a per-site connection model. It isn't on the public roadmap yet, so some open questions we'd be glad to see answered here:

Will the MCP require Elementor Pro, or work with free Elementor?
Does Angie's daily credit limit apply to MCP tool calls, or is the MCP metered separately?
What's the authentication mechanism — application passwords, OAuth, a dedicated token?
What's the tool scope at launch? The demo showed create-page, page settings, composition building, widget schema and publish. Does it also cover Theme Builder templates, global classes and variables, WooCommerce and ACF?
Is there a beta or early-access programme we could join before the September release?

Related existing discussions: "Feature Request: Claude Connector for Elementor + WordPress Site Building" and "AI/MCP-Compatible Widget Schema & Semantic Metadata Layer for Elementor". This request is narrower — it's about permission granularity and multi-site operation rather than the connector itself.

Happy to give structured feedback from real agency use: multi-site setups, client production constraints, and a comparison against what we run today.

Agreement

• I confirm I have read and followed all the guidelines and instructions outlined in the Feature Request form.
• I agree that my discussion may be closed without further action if it doesn't meet all the requirements outlined in the Feature Request form.