Tellagen
← Back to Support Center

Configure Codex for Tellagen Diagnosis

Add the Tellagen MCP server to Codex and check its tools from Tellagen.

GuideLast verified Open Markdown version
On this page

Before you start

Intended audience

Responders who use Codex CLI for local incident investigations.

Required permissions

You need a Tellagen API key with the Local Diagnosis preset. The API key owner needs an active responder seat.

Prerequisites

Procedure

Configure the client

  1. Step 1 of 7

    Select Codex

    Open Settings. The Settings navigation label is Local investigation tools. The page heading is AI diagnostics. Select Codex.

  2. Step 2 of 7

    Copy the install command

    Find the Tellagen MCP card. Select Copy.

    Local investigation tools page with Codex selected and the Tellagen MCP install command.
    Use the command shown for Codex, then check the installed tools. Open full-size image(opens in a new tab)

  3. Step 3 of 7

    Add the MCP server

    Run codex mcp add with the copied environment values and stdio command. Codex stores the server configuration.

    Codex command with safe placeholders

    shell
    codex mcp add tellagen \
  --env TELLAGEN_API_KEY=tllg_YOUR_TOKEN \
  --env TELLAGEN_API_URL=https://YOUR_WORKSPACE.api.tellagen.com \
  --env TELLAGEN_MCP_CLIENT=codex \
  -- npx -y @tellagen/mcp-server@latest

  4. Step 4 of 7

    Add required provider tools

    Install only the provider tools that the incident needs. Keep provider credentials in Codex.

Verify access

  1. Step 5 of 7

    Review the Codex server list

    Run codex mcp list. Make sure that the Tellagen server appears.

    Local configuration check

    shell
    codex mcp list

  2. Step 6 of 7

    Check the tools

    In Tellagen, select Check MCP tools. Paste the prompt into Codex.

  3. Step 7 of 7

    Review the result

    Return to Tellagen. Make sure that required tool cards show INSTALLED and ACCESS OK.

You are done when…

Codex can discover the Tellagen MCP server and its allowed incident tools.

Troubleshooting

Codex shows Auth: Unsupported.

This local connection uses TELLAGEN_API_KEY in the MCP configuration; the status does not mean the Tellagen key is invalid.

No diagnostic tools are available.

Confirm the Codex command was installed and the required local tools are enabled, then run Check MCP tools again.

codex mcp list does not show Tellagen.

Run the copied codex mcp add command again. Existing incident work stays in Tellagen. If the server still does not appear, ask the local client administrator to inspect the Codex configuration.

Tellagen shows ACCESS denied.

Replace the local token with a Local Diagnosis key. Do not remove the saved investigation. If access still fails, ask a workspace manager to review the key scopes.

Related articles

External setup references