Skip to main content

Claude.ai custom connector: authorization succeeds, MCP server rejects the token

  • Nov 19, 2026 11:10 AM UTC
  • 1 reply
  • 5 views

dr.reinhardt
Contributor II
Forum|alt.badge.img

Hi ​@luca.latini  and everyone,

We're connecting our Docebo MCP servers to Claude.ai (personal Pro plan) as a custom connector, following the developer guides for OAuth interactive authentication and MCP client setup.

The Docebo sign-in and authorization succeed, but every MCP request then fails. Claude reports that the account was authorized but no MCP server was found, or the account has no access. It happens on the built-in Learner server and on our custom servers. The user is a Superadmin, and all servers are enabled.

Our platform runs on a custom domain. Two details we noticed:

1. Resource: the protected resource metadata declares the resource as the base domain. Your ChatGPT guide sets Resource to the base domain manually, but Claude sends the full MCP server URL as the resource parameter, with no way to override it.

2. Scope: the 401 from the MCP endpoint returns WWW-Authenticate: Bearer resource_metadata=".../.well-known/oauth-protected-resource/mcp", scope=0. The authorization server lists the scope "api", while the MCP resource lists none.

Has anyone connected Claude successfully on a custom domain? Is there a required resource or scope setting for Claude?

Thanks,

Stéphane

1 reply

luca.latini
Docebian
  • Docebian
  • Nov 19, 2026 7:16 PM UTC

Hi ​@dr.reinhardt 

thanks for reaching out, I'm glad you're looking to connect the MCP server.

Did you set up the connector in Claude using your custom domain?

Feel free to DM me with the url of platform you're using, and I'd be happy to help you troubleshoot.