Elementor MCP Lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELEMENTOR_MCP_LITE_SITES | Yes | Absolute path to the local sites.json configuration file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| elementor_lite_list_sitesA | List configured site aliases and platform names; never expose credentials. |
| elementor_lite_ping_siteB | Perform a single authenticated read; return only connection status. |
| elementor_lite_list_documentsB | List at most ten Elementor document titles, ids and status; no document export. |
| elementor_lite_summarize_layoutB | Summarize supplied JSON node types; never return layout content or settings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Upgrade to Pro | Show Lite/Pro differences; contains no executable Pro functionality. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing sites, checking connectivity, listing documents, and summarizing layout JSON. No overlap or plausible miselection between any pair.
All four tools share the elementor_lite_ prefix and follow a consistent snake_case verb_noun pattern (list_sites, ping_site, list_documents, summarize_layout). Fully predictable.
Four tools is reasonable for an explicitly 'Lite' read-only introspection server, though it sits near the thin end of the acceptable range.
The read-only surface is coherent but stops short of obvious operations like fetching a single document's details or retrieving layout structure; agents cannot go beyond listing and summarizing. Acceptable for a lite scope but leaves notable dead ends.