MCP Authorization
How to authorize an MCP client with Gatana Gateway
There are two methods of authorization an MCP client with the gateway:
- OAuth 2.1: Use Gatana's OAuth 2.1 service to authorize
- Personal Access Token: A static token, managed from Gatana App
OAuth 2.1
To configure a client to use OAuth 2.1 you most often do this by specifying nothing at all. The MCP Client will connect to Gatana and discover authorization is required, and redirect you to sign-in using your standard web-browser automatically.
Example configuration:
{
"Gatana": {
"type": "http",
"url": "https://YOUR_ORG_ID.gatana.ai/mcp"
}
}More Secure
Traditionally OAuth 2.1 has been the more secure method due to how MCP Client often handle static headers versus OAuth credentials. Additionally, the token is only valid for a limited time and sensitive information is commonly stored in the operating system's credential store.
Personal Access Token
This is a more simple method of authorizing. It is a static token added in the HTTP Authorize header. You can configure your PAT:s by navigating to your My Account at the bottom of the left sidebar in the Gatana App.
Example configuration:
{
"Gatana": {
"type": "http",
"url": "https://YOUR_ORG_ID.gatana.ai/mcp",
"headers": {
"authorization": "Bearer THE_PERSONAL_ACCESS_TOKEN"
}
}
}