We currently support the following authentication methods for authenticating between MCP Fabric and the underlying API.
All secrets from the authentication configuration are encrypted at rest in the database and redacted from logs. It is not recommend to manually add secrets to a route as they will not be redacted from logs.
Provide a username and password. These credentials will be included in each request using standard HTTP Basic Authentication.
Provide your API key and specify the header the API expects. The default header is X-API-Key.
GET /v1/things HTTP/1.1
Host: api.example.com
X-API-Key: your-key
Provide the query parameter key and value. The default key is key.
GET /v1/things?key=your-key HTTP/1.1
Host: api.example.com
Provide your bearer token. It will be included in the Authorization header as a Bearer token.
GET /v1/things HTTP/1.1
Host: api.example.com
Authorization: Bearer your-token
Some APIs require OAuth 2.0 for authentication. This method involves a more advanced setup process, so we recommend using one of the simpler options above if possible.
To use OAuth 2.0:
Once connected, MCP Fabric will automatically handle token retrieval and renewal from the underlying auth provider.