What you can ask
Solibo Home MCP lets your AI assistant answer operational questions and prepare changes using the same Solibo Home access rights you already have. You can ask in normal language; the assistant chooses the relevant Solibo tools, narrows the scope when needed, and summarizes the result.
All read examples require solibo.mcp/read. Changes require solibo.mcp/write. Customer newsletters, SMS, letters, and resident-facing publishing require solibo.mcp/communicate when configured for your connector.
What results to expect
- For searches and overviews, expect concise lists, counts, statuses, IDs, and links back to Solibo Home where available.
- For deep dives, expect structured summaries with the most relevant fields, related records, and follow-up options such as opening a conversation, issue, invoice, document, section, or meeting.
- For sensitive data, expect safe defaults. Personal and recipient email addresses, phone numbers, personnummer, registered addresses, KID values, account numbers, policy numbers, loan numbers, and document text are hidden or masked unless there is an explicit scoped reason to reveal them. Explicitly exposed organization, supplier-contact, and company invoice-reception emails outside Solibo-owned domains may be shown when relevant, as may the derived company dedicated address (
<slug>@home.solibo.no). Solibo staff may see Solibo-domain staff emails exposed by a tool. Users outside Solibo receive no accounting-contact records (including names, person IDs, and emails), and see Solibo-domain user emails only for administrator contacts. - For writes, expect a preview first. The assistant should show exactly what will change and wait for your confirmation before saving, sending, publishing, deleting, or externally submitting anything.
- For missing access, expect an explanation that Solibo Home permissions prevented the answer, plus a narrower query you can try.
Getting oriented
Try asking:
| Ask | Expected result |
|---|---|
| “What Solibo access do I have here?” | Your current access, available actions, and whether the session has a working company or broader company scope. |
| “Set Solsiden Borettslag as the working company.” | Confirmation that follow-up company-specific questions will use that company automatically. |
| “Show the companies I can access.” | The companies available to you under the current scope. |
| “What is the current session context?” | The active working company and any broader company scope. |
The assistant may also initialize session context automatically. For example, if you only have access to one company, it can use that company as the working company without asking you to repeat the name.
Company and board questions
Try asking:
| Ask | Expected result |
|---|---|
| “Give me an overview of the companies I can access.” | Company list or dashboard with section counts, board/member indicators, open conversations, tasks, invoices, and operational flags. |
| “Which companies need attention this week?” | A prioritized digest across activity, open conversations, tasks, invoice approvals, meetings, and recent changes. |
| “Find company 123456 and summarize it.” | Matched company profile, board context, tags, ordinances, addresses, and relevant Solibo Home links. |
| “Show the board report for Granly Vel.” | A board-ready summary with company details, board members, sections, residents, open issues, economy status, meetings, documents, and follow-up links. |
| “Which companies have unapproved invoices?” | Companies grouped by unapproved supplier invoice status, with counts and drill-down options. |
You can also ask about board composition, company action strings, by-laws/ordinances, company addresses, section tag taxonomies, and company activity summaries.
People, residents, sections, and board members
Try asking:
| Ask | Expected result |
|---|---|
| “Who sits on the board for the companies I can access?” | Board member list grouped by company, role, and safe person identifiers. |
| “Find person Kari Hansen.” | Matching persons with roles and company relationships, without unnecessary contact identifiers. |
| “Who are the current residents in section 12?” | Current resident/ownership view for that section, with safe names and relationship metadata. |
| “Show section 77 with tags, fractions, loans, and attendance.” | Section deep dive with status, tags, fractions, loan allocation, attendance rows, and related issues or conversations. |
| “Reveal historic resident history for this section for audit review.” | Normal safe section history first; historic resident reveal only after explicit scoped permission. |
Section and resident answers avoid email addresses, phone numbers, personnummer, and registered addresses unless an audited reveal path exists and you explicitly approve the scoped need.
Conversations and customer inquiries
Try asking:
| Ask | Expected result |
|---|---|
| “Which companies have open conversations from the last week?” | Open conversation counts and representative conversations, usually treating NEW and IN_PROGRESS as open. |
| “Show conversations assigned to me.” | Your conversation queue with company, category, status, folder, and last activity. |
| “Find the complaint conversation about parking.” | Matching conversations with participants and a minimized message preview. |
| “I approve showing the full conversation for audit review.” | Full message content through an audited reveal tool after explicit permission. |
| “Reply to the resident with this text.” | Reply preview, recipient/channel context, and confirmation before sending. |
The assistant can also manage conversation categories, folders, participants, external participants, linked documents, linked issues, read state, and publishing when the right permissions and confirmations are present.
Tasks, issues, and meetings
Try asking:
| Ask | Expected result |
|---|---|
| “List overdue tasks in my companies.” | Tasks grouped by company, assignee, due date, status, and priority. |
| “Create a follow-up task for the board meeting next Tuesday.” | Proposed task title, company, due date, assignee if known, and confirmation before creation. |
| “Show open issues for Solsiden Borettslag.” | Issue list with status, responsible person, linked sections/conversations, comments, and next steps. |
| “Open an issue from this conversation.” | Preview linking the conversation to the new issue before saving. |
| “What meetings are coming up?” | Upcoming meetings with company, time, participants, agenda/issues, and signing status where available. |
| “Prepare me for the next board meeting.” | Meeting prep summary with agenda, linked issues, unresolved follow-ups, recent company activity, documents, and economy signals. |
| “Send the meeting summons” | Summons preview and confirmation before sending. |
Meeting tools can also update participants, add or reorder issues, mark issues treated, set follow-up, start/close/reopen meetings, handle signatures, RSVP, and mark attendance.
Economy, supplier invoices, expenses, and reports
Try asking:
| Ask | Expected result |
|---|---|
| “Show the economy status for this company.” | Balance, credit line, accounting status, ledger health, and relevant warnings. |
| “Which invoices need approval?” | Supplier invoice approval counts, company approval status, and backlog when available. |
| “Approve invoice 987 after I confirm.” | Invoice decision preview; approval only after explicit confirmation. |
| “Show expenses awaiting review.” | Expense rows with status, amount, company, submitter reference, and safe details. |
| “Order the quarterly economic report.” | Report-order preview and confirmation before requesting the report. |
Supplier invoice, expense, and report mutations are guarded. Outputs use safe IDs and masked financial identifiers by default.
Documents
Try asking:
| Ask | Expected result |
|---|---|
| “Find board meeting documents from May.” | Document search results with document type, folder, company/object scope, safe metadata, and links where available. |
| “Browse the meeting document folder.” | Folder rows and child documents for the selected document tree. |
| “Get an open link for this PDF.” | A Solibo Home document link when you have access. |
| “Summarize this document.” | Metadata first; extracted document content only after explicit reveal permission when content is sensitive. |
| “Upload this file to the issue document folder.” | Upload target, document type, folder/object scope, and confirmation before creating the document record. |
Document writes include upload, folder creation, object-scoped document creation, rename, move, trash, restore, and delete. Document creator names and document contents use audited reveal paths when needed.
Homepage and resident-facing content
Try asking:
| Ask | Expected result |
|---|---|
| “Show the homepage feed for this company.” | Current feed posts, practical info, notification groups, and safe publishing metadata. |
| “Prepare a feed post about elevator maintenance.” | Exact post text, target company/groups, and confirmation before publishing. |
| “Update the practical info for waste collection.” | Preview of the old/new practical-info content and confirmation before saving. |
| “Attach this uploaded image to the homepage post.” | Uses the uploaded Solibo document as imageDocumentId on the homepage post or practical-info update. |
| “Preview this post across my companies.” | Company-specific substitutions rendered before any resident-visible publish action. |
Resident-facing publishing is treated as communication-sensitive. The assistant should not publish or update content until the text, audience, company scope, and timing are clear and confirmed.
Newsletters, SMS, letters, and delivery reports
Try asking:
| Ask | Expected result |
|---|---|
| “Before sending a resident update, show notification groups and SMS readiness.” | Available recipient groups, SMS package/readiness status, validation warnings, and safe group metadata. |
| “Draft a newsletter to all residents about the maintenance window.” | Draft preview with subject/body, company-specific substitutions, selected groups, and confirmation before draft creation. |
| “Send the draft I just approved.” | Send/publish confirmation using the returned draft IDs; no duplicate confirmation loop when your earlier approval covered the exact send. |
| “Show recent newsletters and SMS broadcasts.” | Communication list with status, published/draft state, delivery summary, and links to details. |
| “Show delivery reporting for this message.” | Aggregate delivery report and per-recipient status where allowed, without exposing recipient email or phone values. |
The assistant can draft and send email newsletters, SMS broadcasts, Solibo letters, company letters, public conversation replies, and meeting summons. It can also update or delete drafts and purchase SMS bundles when enabled and confirmed.
Maintenance, routines, assets, parking, storage, and HMS
Try asking:
| Ask | Expected result |
|---|---|
| “Show HMS settings for this company.” | Current HMS configuration and whether setup is initialized. |
| “List routines for fire safety.” | Routine matches, routine groups, status, schedule, and related assets. |
| “Show parking allocation and vacant spaces.” | Allocation counts, vacant parking spaces, vacancy periods, and selected parking-space details. |
| “Assign parking space 12 to this section.” | Assignment preview and confirmation before changing allocation. |
| “Show storage room B4 and vacancy status.” | Storage room details, allocation status, and vacancy intervals. |
The assistant can create/update/delete routines, initialize or update HMS settings, create/update/delete parking spaces and storage rooms, and assign or unassign assets after confirmation.
Suppliers and organizations
Try asking:
| Ask | Expected result |
|---|---|
| “Find supplier 999888777.” | Global supplier match by name or organization number with safe identifiers. |
| “Which suppliers are connected to this company?” | Company-supplier relationships, categories, comments summary, and safe contact IDs/names. |
| “Add this supplier as the snow-clearing supplier.” | Relationship/category/comment preview before creation. |
| “Show organization employees.” | Organization profile and employee/person rows where you have access. |
| “Add a supplier contact.” | Contact preview and confirmation before saving, without leaking unrelated contact details. |
Supplier and organization workflows cover global supplier search, company supplier relationships, supplier comments and emoticons, contacts, categories, and organization/person drill-downs.
Batch and multi-company workflows
Try asking:
| Ask | Expected result |
|---|---|
| “For the companies I can access, draft a maintenance newsletter with each company’s name.” | Multi-company preview with rendered company-specific substitutions before drafts are created. |
| “Create one feed post per company about elevator work.” | Batch preview by company; confirmed creation only for the reviewed company set. |
| “Prepare tasks for every company missing an approved invoice.” | Proposed per-company tasks and confirmation before creating records. |
For multi-company workflows, the assistant should keep the reviewed company set or active multi-company scope. It should not silently pin an arbitrary working company just because the workflow creates company-specific records.
Explicit reveal requests
Some data is intentionally available only through audited reveal tools. Ask with a specific reason and scope:
| Sensitive request | Expected behavior |
|---|---|
| “Reveal full conversation content for audit review.” | Uses minimized conversation first, then reveals full content only after your explicit permission. |
| “Reveal document content.” | Extracts content only after permission and only for the selected document. |
Broad requests such as “export all identifiers” or “show every resident contact detail” should be refused or narrowed to a masked, scoped report.
Actions that are intentionally guarded
The assistant should always ask for confirmation before it:
- Creates, updates, completes, reopens, closes, deletes, moves, restores, or assigns records
- Sends newsletters, SMS broadcasts, letters, conversation replies, meeting summons, or signature reminders
- Publishes homepage/feed content or updates practical information
- Approves or rejects supplier invoices or expenses
- Orders economic reports or attaches report documents
- Reveals sensitive identifiers or private content through audited tools
If a write capability is not enabled for your connector or your Solibo Home permissions do not allow it, the assistant should explain that limitation and offer the closest read-only review instead.
Outside Solibo Home
Solibo Home MCP should not be used for unrelated questions such as weather, general web search, medical/legal advice, or tasks that do not need Solibo Home data. For those, the assistant should answer normally without invoking Solibo tools.