Skip to main content
Any MCP client that supports remote HTTP transport can connect to TierZero. Pick whichever auth method your client supports.

​
Server details

  • URL: https://api.tierzero.ai/mcp/
  • Transport: Streamable HTTP
  • Auth: OAuth 2.1 or Personal Access Token
If your client supports OAuth 2.1 with dynamic client registration, point it at https://api.tierzero.ai/mcp/ and let it auto-discover the authorization server via /.well-known/oauth-protected-resource. The client will handle the browser-based login flow on first use. This is the same flow Claude Code and Cursor use. No tokens to manage, and access is tied to the user that approved the connection.

​
Option 2: Personal Access Token

Use a PAT for clients that don’t support OAuth, for headless setups (CI, scripts), or when you want long-lived auth tied to a specific user.

​
Generate a token

  1. Go to auth.tierzero.ai/account/api_keys/
  2. Create a new personal API key
  3. Save it somewhere your client can read it, for example as an environment variable:
Treat the PAT like a password. It grants access to your TierZero data. Never commit it to version control or paste it into shared chat.

​
Configure your client

Send the PAT in the Authorization header on every request to https://api.tierzero.ai/mcp/:
The exact config field depends on the client. As an example, for Claude Code’s manual MCP config:
Or in a JSON config like Cursor’s:

​
Rotating or revoking a PAT

Generate a new token at the API keys page and update your client config. Revoke the old one from the same page. There is no automatic expiry — tokens stay valid until you revoke them.