The Elements MCP (Model Context Protocol) server lets your AI assistant securely query your Elements and Salesforce architecture data, using your Elements permissions. This article explains what happens behind the scenes when you connect.
Prerequisites
Elements has enabled MCP access for the Space you want to use. The MCP server is included in the Advanced Metadata Management plan, or in Core Metadata Management with the Agentic Org Management add-on.
You've connected an AI assistant to Elements. See Connect your AI assistant to the Elements MCP server.
One secure endpoint
Your assistant talks to a single Elements address over a secure, authenticated connection. The connection itself stores nothing beyond the sign-in authorization you approved: your password is never shared with your assistant, and no copy of your data is created. There's no separate app or plugin to install on the Elements side; the connection is built into your account.
Uses your existing Elements permissions
A connection never gives your assistant more access than you already have in Elements. Every request is checked against your Elements role, plan and permissions at the moment it's made, so if your access changes, what your assistant can see changes with it.
Per-Space access
When you connect, you choose which Space or Spaces your assistant can use, and it works only in those Spaces. Before a Space can be used at all, Elements must enable it for the MCP server.
What it can access
Your assistant can read your Salesforce metadata and architecture data through Elements: objects, fields, flows, dependencies, access grants, and org-health analytics such as automation, technical debt, compliance and governance.
It can also create and change a limited set of things inside Elements:
A new Space, and selection of the active Space for following calls
A saved metadata view
A process-map or imported diagram draft, and a map copied from a diagram template
Stories and requirements, and their links to Salesforce metadata
A schema inventory
A proposed metadata node: a placeholder marked proposed for people to review, not a change to your org
MetaFields (your own custom fields on metadata), including their values
Everything else is read-only.
Nothing it does ever reaches Salesforce. It never creates, updates, deletes or deploys Salesforce metadata, and it never overwrites your synced reference model. No tool deletes a whole item such as a map or a story.
Some changes inside Elements can overwrite or remove content. Populating a MetaField classification replaces whatever value was there, and narrowing a MetaField's definition can permanently remove values already held in Elements. Diagram imports and removals can also replace or delete diagram content, and story updates and link removals can overwrite story fields or remove links. The six tools labeled Destructive in Elements are revoke_access, update_metafield, manage_diagram, import_diagram, set_story_fields and remove_story_links; their safeguards are listed in the Elements MCP server tools reference.
Publishing an approved diagram version is deliberately not possible through the MCP server; it stays a password-confirmed step in the Elements web app.
Supported clients
The Elements MCP server works with any AI assistant whose MCP client supports remote MCP servers with the MCP standard's secure sign-in (OAuth 2.1 with PKCE). It has been tested with Claude (CLI and Cowork), Codex CLI, ChatGPT (Work) and Cursor. See Connect your AI assistant to the Elements MCP server for setup steps, and Elements MCP server security, data access and admin controls for how to manage or revoke a connection.

