Connecting your AI assistant
Use your existing Solibo Home account to sign in. For assistants where you add the connection yourself, the server URL is:
https://mcp.home.solibo.no
ChatGPT
Open Plugins in ChatGPT, find Solibo Home, and add it. Sign in with your Solibo Home account when prompted.
Claude and Claude Desktop
- Open Customize → Connectors and choose Add custom connector from +.
- Enter
Solibo Homeas the name andhttps://mcp.home.solibo.noas the server URL. - Leave OAuth Client ID and OAuth Client Secret blank. Solibo Home supports dynamic client registration, so Claude registers itself.
- Add the connector, choose Connect, and sign in with Solibo Home.
- Enable Solibo Home from + → Connectors in your conversation.
For Team or Enterprise workspaces, an owner must first add the connector under Organization settings → Connectors. These steps also apply to Claude Desktop. See Claude’s connector guide for details.
Claude Code
Add the server from your terminal. --scope user makes it available in all your projects.
claude mcp add --transport http --scope user solibo-home https://mcp.home.solibo.no
Then run /mcp in Claude Code and authenticate the solibo-home server with your Solibo Home account.
A Solibo Home plugin for Claude Code is awaiting approval in the Claude Community marketplace. Until it is available, add the server as shown above.
Codex
Add the server from your terminal and sign in:
codex mcp add solibo-home --url https://mcp.home.solibo.no
codex mcp login solibo-home
codex mcp login opens your browser; sign in with your Solibo Home account. Codex must run on the computer where you sign in. In a remote environment or a devcontainer, the sign-in cannot return to Codex; see Other MCP clients.
Other MCP clients
Solibo Home only completes a sign-in when it returns to a client we have identified: ChatGPT, Claude (including Claude Desktop and Claude Code), and assistants running on your own computer, such as Codex. This protects your account: a sign-in link can only hand access to a destination Solibo knows, never to an unknown website.
- Assistants on your own computer (desktop and command-line clients): choose a remote connection using Streamable HTTP and OAuth sign-in, and enter the server URL above. The client must support OAuth Authorization Code with PKCE and sign in through a local redirect to
localhost,127.0.0.1or[::1]. Clients that redirect to a custom URL scheme cannot sign in. The client registers itself through dynamic client registration, so you do not need a client ID. - Any other assistant or platform, such as a web-based service that signs in through its own website, must be identified by Solibo before it can connect. Until then its sign-in is refused. Email solibohome@solibo.no with the name of the platform and its exact OAuth callback URL, and we will get back to you.
For services without interactive sign-in, see M2M integration.
Your first conversation
Start with “Use Solibo Home to show the companies I can access.” Once you have chosen a company, try a question that matches your work:
- “Give me a board briefing for Solsiden Borettslag.”
- “Show the latest company news and practical information.”
- “Find the documents for the next board meeting.”
You can follow up on a result without starting over. Ask to open an issue, explain a document, or prepare a task. See Example conversations for complete walkthroughs and What you can ask for more ideas.
If something is missing
If the assistant does not use Solibo Home, check that it is selected for the conversation and mention it explicitly in your request. If sign-in is requested, complete it in the authentication window; do not paste passwords or verification codes into the chat.
If a company or record is unavailable, check which Solibo Home account you used and ask “Which company are we working with?” Your permissions can differ between companies. A connection gives the assistant access through your account; it does not add new permissions. Changes and messages still require confirmation.