Other clients

Datahyena works with any client that supports remote MCP servers over Streamable HTTP with OAuth. The pattern is the same everywhere.

What your client needs

• Server URL: https://api.datahyena.com/mcp
• Transport: Streamable HTTP
• Auth: OAuth 2.1 with PKCE (the client opens a browser for a one-time sign-in)

Most clients accept a server as a small JSON entry:

{
  "mcpServers": {
    "datahyena": {
      "url": "https://api.datahyena.com/mcp"
    }
  }
}

Some clients use a different key for the URL (for example httpUrl or serverUrl) or expect a CLI command such as <client> mcp add datahyena --url https://api.datahyena.com/mcp. Check your client's MCP documentation for the exact field.

Authorization

On the first tool call the client opens your browser. Sign in, choose a workspace, and approve. The client stores the resulting token and refreshes it automatically. You can revoke the connection any time from the dashboard.

Discovery

For agents that auto-discover servers, the OAuth and resource metadata are published at:

https://api.datahyena.com/.well-known/oauth-authorization-server
https://api.datahyena.com/.well-known/oauth-protected-resource

A machine-readable server card is also available at /.well-known/mcp/server-card.json.