Compatibility evidence

This page records concrete MCP client evidence for trello-mcp. It is a dated validation record, not a promise that every client has been fully exercised on every release.

Last updated: 2026-08-09.

Evidence labels

The table keeps four different claims separate:

Official docs reviewed means the linked vendor documentation was checked for the current configuration shape. It does not prove the client was run.
Client connected means that named client completed MCP initialization with the built server over the stated transport.
Tools discovered means the client completed tools/list; where available, the client UI or CLI was also checked for the 77 registered tools.
Live Trello workflow means a tool actually contacted Trello. Startup, health checks, initialization, and tools/list do not contact Trello.

No row is promoted from one state to another by inference alone. VS Code is a documentation-reviewed recipe, not client-run evidence. The OpenCode row expressly labels the one owner-approved assumption in the 2026-08-07 validation pass.

2026-08-07 validation environment

Host: macOS 26.6 (25G72), Apple silicon (arm64).
Runtime: Node.js 24.17.0, pnpm 10.34.1 through Corepack.
Server: a clean build of the issue branch, with no runtime changes from its origin/main base at the time of validation.
Tool surface: 77 registered tools.
Discovery credentials: dummy Trello values. No Trello tool was invoked during discovery.
HTTP auth: an unauthenticated /mcp request returned 401; authenticated Streamable HTTP discovery succeeded with the configured bearer header.

Current validation record

Client	Official docs reviewed	Installed client and transport	Client connected	Tools discovered	Live Trello workflow	Restart requirement, limitation, or blocker
Codex CLI	Yes, 2026-08-07: MCP documentation	Codex CLI `0.146.0` (Homebrew); macOS; `stdio` and Streamable HTTP with bearer auth	Yes on both transports through session-only configuration.	Yes. `/mcp` displayed all 77 tools for each entry.	No. No Trello tool was called.	The default asdf `codex` shim on this host had no configured version, so validation used the explicit Homebrew binary. Session-only configuration left the shared config unchanged.
Claude Code	Yes, 2026-08-07: MCP documentation	Claude Code `2.1.212`; macOS; `stdio` and Streamable HTTP with bearer auth	Yes on both transports.	Yes. `/mcp` displayed all 77 tools for each temporary entry.	No. No Trello tool was called.	Start a new session if an active one does not reload configuration. Temporary entries were removed and the pre-test config was restored byte for byte.
Claude Desktop	Yes, 2026-08-07: desktop extensions and manual JSON	Claude Desktop `1.26832.0`; macOS; `stdio`	Yes. A full app launch initialized the existing user-local `trello` entry and connected to the built server.	Yes. Claude Desktop issued `tools/list` successfully. The exact 77-tool count was corroborated against the same built artifact with Inspector; Claude Desktop’s log does not print the result body.	No. No Trello tool was called.	Fully quit and reopen after config changes. Current official guidance emphasizes MCPB desktop extensions, but this repository has no `.mcpb` package; the tested manual `stdio` entry remains the documented path. No HTTP bearer path is claimed.
VS Code	Yes, 2026-08-09: MCP server guide and configuration reference	Not exercised for this record; current `stdio` and Streamable HTTP configurations reviewed and syntax-checked	Not tested.	Not tested.	No. No Trello tool was called.	Use MCP: List Servers to start, restart, and inspect output. The documented password-input recipes target desktop VS Code; Agent Host does not forward servers that require interactive inputs.
OpenCode	Yes, 2026-08-07: MCP servers	Not installed; current `stdio` and Streamable HTTP configurations reviewed and syntax-checked	Not tested.	Not tested.	No.	The current configuration requires entries under `mcp.servers`, uses `disabled` rather than `enabled`, and groups MCP tools in Code Mode by default. Relaunch after config edits.
MCP Inspector	Yes, 2026-08-07: Inspector documentation	`@modelcontextprotocol/inspector` `2.0.0`; Node.js `24.17.0`; `stdio` and Streamable HTTP with bearer auth	Yes on both transports.	Yes. `tools/list` returned exactly 77 tools on both transports.	No. No Trello tool was called.	No restart required. The guide uses an ignored, read-only Inspector config so credentials do not appear in process arguments. `--cli` must be the first Inspector argument. Version 2.0.0 requires Node.js `22.19.0` or newer.

Named-client test details

Codex

The Homebrew Codex CLI was launched with session-only configuration overrides; the shared ~/.codex/config.toml was not edited. The stdio and bearer-protected Streamable HTTP entries both initialized, and /mcp enumerated all 77 tools for each one.

The explicit Homebrew binary was used because the unrelated default asdf shim did not have a Codex version configured in this checkout. That local shim issue does not affect the documented TOML or codex mcp syntax.

Claude Code

An isolated JSON file copied the guide’s project-level shapes, including the ${...} environment references, and Claude Code loaded it with --strict-mcp-config. Its two entries targeted the built server:

stdio: Claude Code launched node dist/index.js with TRANSPORT=stdio and dummy Trello values.
Streamable HTTP: Claude Code connected to /mcp and sent the required bearer header.

The interactive /mcp view enumerated the same 77 tools for each transport. Separate temporary user entries confirmed that claude mcp list also reported both connections healthy. All temporary files and entries were removed after validation, and the original user configuration was restored exactly.

Claude Desktop

The installed app was launched with its existing user-local stdio configuration. Its MCP log recorded successful server startup, initialization, and tools/list. The configured server artifact was byte-identical to the build enumerated independently as 77 tools. The MCP transport was then closed without changing its configuration.

The current Claude Desktop documentation centers on installable .mcpb desktop extensions. This repository does not contain an MCPB manifest or package, so a one-click extension could not be tested without expanding the issue into a new packaging deliverable. The guide states that limitation plainly and documents the tested manual stdio path.

VS Code

VS Code was not run for this compatibility record. Microsoft’s current MCP server guide and configuration reference were reviewed on 2026-08-09, and the guide’s stdio and Streamable HTTP JSON examples were syntax-checked. The password inputs, user-profile configuration, trust prompt, server commands, and Agent Host limitation therefore remain configuration evidence only.

OpenCode

OpenCode was not installed on the validation host. Its current official documentation was reviewed, and every JSON example was syntax-checked. Direct connection and tool-discovery validation were not performed, so this record makes no client-compatibility claim beyond documentation and syntax review.

MCP Inspector

Inspector 2.0.0 initialized the built server over both transports. Each tools/list --format json result contained 77 tools. The guide’s ignored --config form was tested for both named entries. The HTTP test used a dummy server bearer token; a separate request without that header returned 401.

This is direct transport and tool-discovery evidence. It is not evidence that a Trello workflow ran.

Live Trello workflow status

No live Trello tool was invoked from any named client during the 2026-08-07 pass. The repository’s live-validation safety gate requires all of the following before any Trello request:

TRELLO_LIVE_SMOKE=1
TRELLO_API_KEY
TRELLO_TOKEN
TRELLO_LIVE_SMOKE_BOARD_ID or TRELLO_LIVE_SMOKE_BOARD_URL

The local named-client pass did not have the explicit live-smoke opt-in plus a confirmed disposable board. Discovery therefore used dummy values and stopped at tools/list. That is the intended safe behavior, not a successful live Trello workflow from a named client.

Separately, a secret-backed GitHub Actions Live Trello Smoke run passed during the 2026-08-07 PR validation. The repository harness covered authentication, board/list/card reads, disposable mutations, and cleanup through the registered tool handlers. This is server-harness evidence only; it is not attributed to any named client and does not change the No entries in the table’s Live Trello workflow column.

When a disposable board and explicit opt-in are available, follow the live validation instructions. Never run write-side validation against an ordinary board.

Documentation and visual review

The canonical Set up your MCP client guide contains the sanitized configurations used by this compatibility record. JSON snippets were checked with jq; Codex TOML entries were loaded by the actual Codex CLI; and the Inspector commands were executed against the built server.

No client screenshot was committed. The genuine installed-client views also contained unrelated user configuration and would expose details unrelated to the sanitized configuration examples. The public documentation uses only purpose-built diagrams with no credentials, private UI, or machine-specific paths.