Skip to main content

MCP API

Igdrasil exposes a hosted MCP server for approved agent clients.

Endpoint​

Use the hosted Streamable HTTP endpoint:

https://accounting.igdrasil.se/api/mcp

The server name is igdrasil-mcp. New clients should use /api/mcp; any compatibility aliases should resolve to the same hosted server.

Authentication​

OAuth is the default public setup path. MCP tokens should be issued for the igdrasil-mcp resource or audience. Hosted clients authenticate with:

Authorization: Bearer <mcp-token>

The OAuth discovery and client-setup flow is based on the repository setup guide in docs/agent-harness/igdrasil-mcp-client-setup.md.

Tool discovery​

Prefer the dynamic router when a client would otherwise load too many schemas:

  • igdrasil_search_tools
  • igdrasil_get_tool_schema
  • igdrasil_get_tool_policy
  • igdrasil_call_tool

Direct tools and dynamic router calls use the same policy gates. Write-capable tools still require the required scopes and approval/idempotency safeguards.

Company MCP keys​

The OpenAPI reference includes managed company MCP key lifecycle endpoints under /api/v1/companies/{company_id}/mcp-key and /api/v1/companies/{company_id}/mcp-key/status. Use those only when Igdrasil has explicitly enabled a workspace-managed key path for the company.

For public MCP client setup, prefer OAuth. Rotate or revoke company keys when a client, device, or workspace owner changes.