# Configure MCP tools for Diagnosis

Connect only the provider tools that a local client needs. An MCP server gives the client a standard way to call a provider tool.

## Before you start

### Intended audience

Responders who connect monitoring or infrastructure MCP tools to a local client.

### Required permissions

Tellagen does not receive provider secrets. Your local client controls provider access.


### Prerequisites

- Configure Tellagen MCP in [Codex](https://tellagen.com/help/configure-codex-for-diagnosis) or [Claude](https://tellagen.com/help/configure-claude-for-diagnosis).
- Know which evidence sources the incident requires.
- A local client is Codex or Claude running on your computer.
- A provider tool gives that client access to one evidence source. A wrapper lets one supported card use an existing local CLI or SSH session.

## Procedure

<a id="phase-choose-the-evidence-tool"></a>

### Choose the evidence tool

<a id="step-open-the-tool-gallery"></a>

1. **Open the tool gallery.** Open Settings. The Settings navigation label is Local investigation tools. The page heading is AI diagnostics. Find the provider card you need.

<a id="step-review-the-access-boundary"></a>

2. **Review the access boundary.** Match the card's capability to the evidence question. Prefer read-only provider access.

<a id="step-copy-the-client-command"></a>

3. **Copy the client command.** Select Copy on the provider card. Run the command in the selected local client.

<a id="phase-verify-access"></a>

### Verify access

<a id="step-check-local-discovery"></a>

4. **Check local discovery.** Select Check MCP tools. Paste the prompt into your local client.

<a id="step-review-the-card-status"></a>

5. **Review the card status.** Return to Tellagen. Installed and Access OK prove that the current Check MCP tools result found the tool and reached its provider. Review Not checked by local LLM and stale results before use.

![Local MCP tool cards with install state, access state, stale warnings, and setup commands.](https://tellagen.com/help/assets/diagnosis-tool-status-gallery-2026-08-29.webp)

Review both installation and access before a local investigation uses a provider tool.

<a id="phase-keep-the-tool-set-minimal"></a>

### Keep the tool set minimal

<a id="step-review-wrapper-tools"></a>

6. **Review wrapper tools.** The CLI or SSH wrapper applies only to the Local host diagnostics card. Use it only when existing local authentication has reviewed read-only access. No MCP installation is required for that card.

<a id="step-limit-the-tool-set"></a>

7. **Limit the tool set.** Remove tools that the investigation does not need. Keep credentials outside Tellagen.

## You are done when…

The client exposes required read-only evidence tools without sending provider secrets to Tellagen.

## Troubleshooting

<a id="troubleshooting-a-tool-is-available-but-not-checked"></a>

### A tool is available but not checked.

Run Check MCP tools after installing it. Availability alone does not prove that the local credential works.

<a id="troubleshooting-the-required-provider-is-not-in-the-gallery"></a>

### The required provider is not in the gallery.

Do not install an arbitrary server from this guide. Ask a workspace settings administrator to review the request. If the provider is still unsupported, email [Tellagen support at support@tellagen.com](mailto:support@tellagen.com).

<a id="troubleshooting-the-card-is-installed-but-access-fails"></a>

### The card is installed but access fails.

Make sure that the local credential can read the listed provider resources.

<a id="troubleshooting-a-status-is-stale"></a>

### A status is stale.

Run [Check MCP tools again](https://tellagen.com/help/run-local-diagnosis#step-check-local-setup) before the investigation.

## Related articles

- **Recommended next task:** [Run a local Diagnosis for an incident](https://tellagen.com/help/run-local-diagnosis)
- [Configure Codex for Tellagen Diagnosis](https://tellagen.com/help/configure-codex-for-diagnosis)
- [Configure Claude](https://tellagen.com/help/configure-claude-for-diagnosis)


## Continue through the incident lifecycle

- **Previous task:** [Configure Claude for Tellagen Diagnosis](https://tellagen.com/help/configure-claude-for-diagnosis)
- **Next task:** [Configure a supported integration](https://tellagen.com/help/configure-integrations)
- [Back to Support Center](https://tellagen.com/help#help-search)

## Last verified date

2026-08-29