H
Hjarni MCP server
Details
- Endpoint
-
https://hjarni.com/mcp - Transport
- streamable-http
- Docs
- https://hjarni.com/docs/mcp
Authentication
OAuth · resolves from well-known metadata For MCP clients that support OAuth, use Hjarni's OAuth 2.0 Authorization Code flow with PKCE discovered from OAuth authorization server metadata. Hjarni supports dynamic client registration at register; hosted clients may also use pre-approved redirect URIs documented in the MCP reference. Authorize the user via authorize and exchange the code at token.
Authorization: Bearer <credential> In Hjarni, go to Settings > Connections, create a token for your integration, and copy it. The REST API docs say to send it as Authorization: Bearer YOUR_API_TOKEN. The same personal API token can also be used against the MCP endpoint for clients that do not support OAuth. Start from the REST API reference.