Connecting your AI assistant

Solibo Home MCP works with any MCP-compatible client that supports OAuth sign-in. You’ll use your existing Solibo Home credentials — no separate account needed.

ChatGPT

ChatGPT can connect to Solibo Home as a manually configured app.

  1. Open ChatGPT, open Settings, choose Apps, and enable Developer mode. Keep Enforce CSP in developer mode enabled.

    ChatGPT Apps settings with Developer mode enabled

  2. Choose Create app.

  3. In New App, enter:

    Field Value
    Name Solibo Home
    Connection Server URL
    Server URL https://mcp.home.solibo.no
    Authentication OAuth
  4. Check I understand and want to continue.

  5. Click Create.

    ChatGPT New App dialog configured for Solibo Home

  6. Start using the app. ChatGPT will ask you to sign in with your Solibo Home credentials the first time it needs access.

ChatGPT discovers the OAuth configuration from the Solibo Home MCP server. You should not need to fill in the advanced OAuth settings manually.

Claude

Claude can connect to Solibo Home as a custom connector.

  1. Open Claude settings and go to Connectors.
    • In Claude Team or Enterprise, organization Owners can use Organization settings > Connectors.
    • In Claude Pro or Max, use Customize > Connectors.
  2. Choose Add custom connector.

  3. Enter:

    Field Value
    Name Solibo Home
    Server URL https://mcp.home.solibo.no
  4. Leave OAuth Client ID and OAuth Client Secret blank.

  5. Click Add, then connect the new connector and sign in with your Solibo Home credentials.

    Claude custom connector dialog configured for Solibo Home

Claude Desktop

For local Claude Desktop configuration, add Solibo Home to your Claude MCP server configuration:

{
  "mcpServers": {
    "solibo-home": {
      "url": "https://mcp.home.solibo.no"
    }
  }
}

Claude Desktop discovers the sign-in flow automatically. On first use it will open a browser window for you to authenticate with your Solibo Home account. Hosted Claude surfaces use https://claude.ai/api/mcp/auth_callback as their OAuth callback URL; the production server accepts this through its claude provider redirect policy.

Other MCP clients

Any MCP client that supports the Streamable HTTP transport and OAuth 2.1 Authorization Code + PKCE should work. Point the client at https://mcp.home.solibo.no — it will receive a sign-in challenge and discover the authorization server automatically.

Native desktop clients that use loopback OAuth callbacks are supported for localhost, 127.0.0.1, and [::1]. Hosted AI assistants need either an exact callback URL in OAUTH_REDIRECT_URIS or a narrowly scoped provider policy in OAUTH_REDIRECT_PROVIDERS.

Permissions

What the assistant can see and do depends on which scopes were granted at sign-in:

Scope Grants access to
solibo.mcp/read All read/query capabilities
solibo.mcp/write Confirmed changes to tasks, issues, meetings, conversations, documents, economy records, sections, suppliers, homepage content, assets, and other Solibo Home records
solibo.mcp/communicate Drafting, sending, publishing, and reporting resident/customer communications such as newsletters, SMS broadcasts, letters, public replies, and meeting summons

Your Solibo Home access rights apply on top of these scopes — the assistant can only access companies and data that you can access.

Solibo AS