### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? Summary The "ElevenLabs Agents MCP App" connector fails every call with a 401 invalid_api_key error, even though the underlying ElevenLabs API key is conf

[BUG] ElevenLabs Agents MCP connector returns 401 invalid_api_key, persists through reconnect and app restart

Status Open

Reported on v2.1.227

Maintainer reply None cached

Workaround ✓ Mentioned in description ↑

Activity 0 comments · opened Aug 23, 2026

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report (please file separate reports for different bugs)
[x] I am using the latest version of Claude Code

What's Wrong?

Summary
The "ElevenLabs Agents MCP App" connector fails every call with a 401 invalid_api_key error, even though the underlying ElevenLabs API key is confirmed valid and unrestricted.

Steps to reproduce

Have the ElevenLabs Agents MCP App connector configured and previously working.
Call any tool on it (e.g. get_agent_config).
Observe: Status code: 401 ... "message": "Invalid API key", "status": "invalid_api_key".

What we tried

Disconnected and reconnected the connector — same 401 afterward.
Fully quit and restarted the Claude Code app — same 401 afterward.
Verified the ElevenLabs API key directly against the real ElevenLabs API (api.elevenlabs.io) with a plain curl request — key is valid, unrestricted, and returns 200.

Conclusion
The credential itself is fine; the fault sits in the MCP connector/bridge, not the ElevenLabs account or key. As a workaround we called the ElevenLabs REST API directly instead of via the connector.

Impact
Blocks any workflow relying on this connector for ElevenLabs agent config reads/writes.

What Should Happen?

The connector should authenticate successfully and return the agent config, since the underlying ElevenLabs API key is valid and works when called directly.

Error Messages/Logs

Status code: 401
Body: {
  "detail": {
    "type": "authentication_error",
    "code": "unauthorized",
    "message": "Invalid API key",
    "status": "invalid_api_key",
    "request_id": "bbae8cd20c663be1d2efe9fbc3be0a68"
  }
}

Steps to Reproduce

Have the ElevenLabs Agents MCP App connector configured and previously working.
Call any tool on it (e.g. get_agent_config).
Observe the 401 invalid_api_key error above.
Disconnect/reconnect the connector — same result.
Fully quit and restart the Claude Code app — same result.
Call the same ElevenLabs API key directly via curl against api.elevenlabs.io — succeeds (200).

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.227

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

The credential was independently verified as valid outside the connector: a direct curl request to https://api.elevenlabs.io/v1/convai/agents/{agent_id} using the same, unrestricted ElevenLabs API key returned 200 OK. This isolates the fault to the MCP connector/bridge itself, not the ElevenLabs account, the key, or its permissions. As a workaround, we're calling the ElevenLabs REST API directly instead of through the connector.

View original on GitHub ↗