MCP server authentication for an internal agent
We are building an internal agent against the MCP server. Does it use the same API key as the REST API, or a separate credential?
We are building an internal agent against the MCP server. Does it use the same API key as the REST API, or a separate credential?
Same API key as the REST API, scoped exactly the same way, an internal agent authenticates against the MCP server with no separate credential to manage.
Same API key as the REST API, scoped exactly the same way, an internal agent authenticates against the MCP server with no separate credential to manage.
Good to know, wired our internal agent up with the same key we use for REST calls.
Worth mentioning the key scopes apply the same way over MCP too, a read only key cannot make writes through either surface.
Good to know, wired ours up the same way without issue.
Appreciate the clarification on scopes carrying over, that was not obvious from the docs.
If anyone hits a scope mismatch between REST and MCP, that would be a bug, please flag it.
Testing this demo forum as public member
Sign in to reply to this question.