> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Access for Apps and Elements

> Enable local coding agents such as Claude Code to discover and work with records in configured Apps and Elements through Elementum's MCP server.

Local coding agents can connect to Elementum through an organization-level Model Context Protocol (MCP) server to search, read, create, and update records in Apps and Elements that App Administrators have enabled for MCP.

Each user who connects a client authenticates with their own Elementum account and acts with their own permissions. Record actions appear under that user's identity.

## Prerequisites

* **App Administrator** access to enable and configure MCP for each App.
* A local MCP-compatible coding client. Claude Code is supported; additional clients are being added.
* MCP access is off by default for every App. An App Administrator must enable it before clients can discover or change that App's records.

## Enable MCP for an App

1. Open the App → **Intelligence** → **MCP**.
2. Turn on **Enable MCP access**. When this is off, the App is hidden from object discovery and new record requests are rejected.
3. Under **Object guidance**, set a **Short description** (shown when a client lists available objects) and **Agent instructions** (returned when a client describes the object).
4. Click **Save changes**.

## Configure allowed record operations

1. Under **Allowed record operations**, enable **Read records**, **Create records**, and/or **Update records**.
2. Click **Configure** next to **Read records**. Mark which fields are **Included** on search and read responses, and which of those are **Searchable**. Click **Apply configuration**.
3. Click **Configure** next to **Create records**. Choose which additional fields the create tool accepts and whether each is required beyond system-required fields. Click **Apply configuration**.
4. Click **Configure** next to **Update records**. Choose which fields are editable through MCP. Click **Apply configuration**.
5. Use the **Tool API Preview** on the right to inspect the contract for tools such as `list_entities`, `describe_entity`, `search_records`, `read_record`, `create_record`, and `update_record`.
6. Click **Save changes**.

## Connect a client

1. On the App **MCP** page, click **Connect** to open **Connect an AI client**.
2. Copy the Claude Code command and run it in your terminal to add the organization MCP server.
3. In Claude Code, enter `/mcp`, select the connection name, and complete the OAuth sign-in to approve access.
4. Ask the client to list Apps or Elements and read a record to verify the connection.

## Behavior notes

* Search uses only fields marked searchable and typically returns a compact set (for example ID, title, and status). The client uses `read_record` when it needs additional included fields.
* Create always includes system-required fields; you choose any additional create fields and whether they are required or optional.
* Clients discover every MCP-enabled App and Element the signed-in user can access. Disabling MCP on an App hides it from discovery without affecting other Apps.
* Record actions run as the authenticated user through the OAuth flow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.