Machine-to-machine integration

Connect your service or automation directly to Solibo Home MCP without an interactive sign-in. Contact Solibo for a client ID, client secret, and access to the companies and tools your integration needs.

Get an access token

Request a token using your provisioned credentials:

curl -sS https://auth.home.solibo.no/oauth2/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "grant_type=client_credentials" \
  --data-urlencode "client_id=<client_id>" \
  --data-urlencode "client_secret=<client_secret>" \
  --data-urlencode "scope=solibo.mcp/read"

Use the returned access_token as a bearer token. Keep credentials and tokens in your service’s secure configuration.

Call the MCP server

Use an MCP client with Streamable HTTP and bearer-token support, or follow this request sequence. Replace the placeholders with your token and session ID.

First, initialize the connection:

curl -sS -i https://mcp.home.solibo.no \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "initialize",
    "params": {
      "protocolVersion": "2025-11-05",
      "capabilities": {},
      "clientInfo": {"name": "my-service", "version": "1.0"}
    }
  }'

Reuse the returned Mcp-Session-Id header on subsequent requests. Complete initialization:

curl -sS https://mcp.home.solibo.no \
  -H "Authorization: Bearer <access_token>" \
  -H "Mcp-Session-Id: <session_id>" \
  -H "MCP-Protocol-Version: 2025-11-05" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "method": "notifications/initialized"}'

Then discover the tools available to your integration:

curl -sS https://mcp.home.solibo.no \
  -H "Authorization: Bearer <access_token>" \
  -H "Mcp-Session-Id: <session_id>" \
  -H "MCP-Protocol-Version: 2025-11-05" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 2, "method": "tools/list"}'

Make your first tool call

Use tools/call with a tool name and arguments from its returned schema. For an account-data workflow, begin by loading the session context:

curl -sS https://mcp.home.solibo.no \
  -H "Authorization: Bearer <access_token>" \
  -H "Mcp-Session-Id: <session_id>" \
  -H "MCP-Protocol-Version: 2025-11-05" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0", "id": 3, "method": "tools/call",
    "params": {"name": "initialize_session_context", "arguments": {}}
  }'

The result provides the accessible company context for subsequent queries. Use IDs from returned records when calling other tools, and follow each tool’s input schema. Reusing the session also preserves session shortcuts.

For a first integration, start with a read-only workflow such as a company briefing or an overdue-task report. Check error and completeness information in the response before treating it as a full result.

Scopes and permissions

Scope Purpose
solibo.mcp/read Read tools available to your integration
solibo.mcp/write Confirmed changes, when provisioned
solibo.mcp/communicate Confirmed communications, when provisioned

Request only the scopes you need. Solibo Home access restrictions and the preview/confirmation flow still apply; see What you can ask.

Solibo AS