Kliva

    Functions/MCP

    Model Context Protocol for property data

    MCP makes Kliva's Nordic property data available as secure context in MCP clients like Claude, ChatGPT, and Microsoft Copilot. No copies, no insecure exports, and access control on every call.

    Vision · MCP

    The hub for future AI development.

    AI does not replace real estate systems; it enhances their value. AI quality depends on the connected data it uses. Kliva MCP is the neutral data and agent layer where industry AI connects:Verified data in, trusted agents out.

    01 — Connected data

    Verified real estate data in one hub

    Ownership, rents, transactions, climate and company data — always with a stated confidence level and source.

    02 — The CRM hub

    The place where all information converges

    Pipelines, contacts, property relations, and processes — integrated with data and AI flows.

    03 — AI / MCP gateway

    Agent layer on top of the hub

    A neutral protocol layer allowing agents and apps to build on Kliva — live today.

    "The more AI, the more critical a central, connected platform becomes."

    Each connection is individually secured. Auth0 binds every call to a verified identity with assigned rights — no shared tokens, no anonymous sessions.

    What MCP enables

    Fem datadomäner — i naturligt språk.

    Transaction & market

    Comparable deals, yield trends, and benchmarks across the Nordics.

    The built environment

    Properties, buildings, ownership, technical, and spatial attributes.

    Early stages

    Zoning plans, building permits, and municipal decisions – via Byggfakta.

    Tenant intelligence

    Demographics, visitor flows, and establishment analysis.

    Climate, risk & environment

    Climate benchmarks, exposure, and taxonomy-aligned analysis.

    Why graph + AI belong together

    A traditional relational database forces properties, owners, detailed development plans, and transactions into separate tables that must be joined for every query. The more hops — from property to owner to group to other holdings — the slower and more fragile the result.

    This is also why the model is the right match for AI. Large language models reason in entities and relations — the same structure as the graph. When an agent queries via our MCP server, it receives nodes and edges rather than table rows it must piece together. The context becomes smaller, answers more traceable, and the risk of hallucinations lower.

    Silver & gold — never raw data

    All data served by MCP has passed Kliva's quality pipeline: cleansed, validated, enriched.

    Auth0 per user

    No data leaves Kliva without verified identity and assigned rights.

    Data in Sweden · ISO 27001

    The entire data flow is within Swedish territory and enterprise security frameworks.

    Pilot · Open nowFirst come, first served

    5 slots.
    Shape the next generation of real estate AI.

    Kliva MCP is opening for a limited pilot program — selected customers who want to build future AI-driven real estate intelligence with us. The pilot closes when slots are filled.

    We ask you to commit

    • 01Two interviews during the pilot period
    • 02Documented use cases from your daily work
    • 03Willingness to share publicly as a reference or case study

    The pilot period captures insights from your daily work — and allows us to show the industry what becomes possible when verified data meets agents.

    MCP-server

    Connect your AI agent to Nordic property data

    The Property Graph is available for your AI agents via our MCP-server. This includes the same nodes, relations, and verified data your team uses within the platform. No copying, no export file.

    Read the documentation

    MCP Security

    Controlled access, not open data exposure

    Kliva's MCP support is designed around established security patterns: OAuth-based authorization, strong authentication with MFA, and clear limits on the context an AI client may use.

    Verified Identity

    Each connection is initiated via an OAuth flow, Auth0, and MFA before an AI client can request context from Kliva.

    Least Possible Access

    Access is limited per user, client, and purpose. The client receives only the context needed for the current query.

    Traceable Usage

    Calls can be logged, linked to the correct user, and audited afterwards for compliance and incident management.

    MCP Compatibility

    Kliva data for your AI assistants

    Model Context Protocol allows Claude, ChatGPT, Copilot, and other MCP-compatible clients to retrieve the correct property context from Kliva — with permissions, logging, and control for each call.

    Claude logo
    ChatGPT logo
    Microsoft Copilot logo

    Security Across the Protocol

    Auth0, MFA, and Policy-Driven Access

    Auth0 logo

    OAuth-based authentication for MCP clients.

    MFA and permissions before data leaves Kliva.

    Traceable calls, scopes, and data integrity per user.

    Confidence

    Verified for machines

    Varje svar från Kliva MCP bär samma källhänvisning och konfidensnivå — Guld, Silver, Brons — som i plattformen. Era agenter gissar inte; de citerar riktig data.

    Guld

    Guld

    Directly from the primary source — registry data, title deed transfers, current zoning plans. Verified and referenced.

    Silver

    Silver

    Derived from multiple sources or with a known delay — clearly marked with the underlying data.

    Brons

    Brons

    Modeled or estimated — with stated assumptions, never presented as absolute fact.

    Quickstart

    Connect your AI clients to Kliva in four steps

    The same basic flow applies to Claude, ChatGPT, and Copilot: add Kliva's MCP server, authenticate with Auth0, verify MFA, and assign the client correct permissions.

    Claude logo
    1. 01Open Claude and go to MCP or connectors settings.
    2. 02Add Kliva's MCP server and select Auth0 as the login flow.
    3. 03Log in with MFA and approve the Kliva scopes your team will use.
    4. 04Test by asking for a property, transaction, or portfolio context.
    ChatGPT logo
    1. 01Create a new connector or custom tool in the ChatGPT environment.
    2. 02Enter Kliva's MCP endpoint and link authentication via Auth0.
    3. 03Complete MFA and restrict access with the correct scopes for the user.
    4. 04Verify that ChatGPT can retrieve current Kliva data without file import.
    Copilot logo
    1. 01Open Copilot Studio or your Microsoft 365 Copilot configuration.
    2. 02Register Kliva as an MCP source for property data and analysis context.
    3. 03Connect Auth0, require MFA, and map users to Kliva permissions.
    4. 04Publish to the correct team and test queries with actual permissions.

    FAQ

    Common Questions About MCP

    What you get

    All key information, gathered in one feed

    MCP kopplar ihop data och analys så att teamet kan gå från insikt till beslut med mindre handpåläggning.

    01

    Works with Claude, ChatGPT, and Copilot

    02

    Standardized Model Context Protocol

    03

    Correct property context directly in the AI flow

    04

    Auth0 and MFA over the MCP protocol

    05

    Permission-controlled scopes per user

    06

    Logging and data integrity in each call

    Kliva

    Kliva support

    We usually reply within minutes

    Hi, how can we help?

    Ask a question or pick a shortcut below.