How to connect Elasticsearch to Codex

1. 1. Enable Elasticsearch in Metorial

   In your Metorial portal, enable the Elasticsearch MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

2. 2. Add the server and sign in

   The Codex CLI, IDE extension and ChatGPT desktop app share this config.

   Copy

   codex mcp add metorial --url <your-magic-mcp-url>
   codex mcp login metorial

3. 3. Check the connection

   Type /mcp in Codex to see Metorial and its Elasticsearch tools.

• Cluster Health: Get the health status and key metrics of the Elasticsearch cluster including node count, shard allocation status, and pending tasks.
• List Indices: List all indices in the Elasticsearch cluster with their health status, document count, and storage size.
• Get Document: Retrieve one or more known Elasticsearch documents by ID.
• Bulk Operations: Perform multiple index, create, update, or delete operations in a single API call.
• Index Document: Create or replace a document in an Elasticsearch index.
• Update Document: Partially update an existing document in an Elasticsearch index.
• Manage Index: Create, configure, open, close, or delete an Elasticsearch index.
• Search Documents: Search and query documents in Elasticsearch using the full Query DSL.
• Manage Watch: Create, update, delete, execute, activate, or deactivate Watcher alerts.
• Manage Alias: Create, delete, or list index aliases.
• Graph Explore: Discover relationships between terms in an Elasticsearch index.
• ES|QL Query: Execute an ES|QL query to filter, transform, and analyze data stored in Elasticsearch.
• Manage Snapshot: Create, restore, delete, or retrieve snapshots and snapshot repositories for cluster backups.
• Reindex: Copy documents from one index to another, optionally applying a query filter or transformations via a script.
• Run Inference: Execute a machine learning inference task using a configured inference endpoint.
• And 5 more on the Elasticsearch MCP server page.

• Limit which Elasticsearch tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
• Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
• Type /mcp in the composer to see the connected servers.
• Override the approval behavior for a single Elasticsearch tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Metorial times out at startup

Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.

Long tool calls fail after a minute

The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.