Skip to main content

​
Overview

No exports, filters or separate reporting tools required. The Abisko MCP (Model Context Protocol) connector lets you query your Abisko data directly from your AI Client (e.g. Claude). Once connected, you can ask Claude questions about your portfolio in plain language, and it will provide you with accurate answers by looking up live data from Abisko.

​
What you can do

Once connected, ask Claude things like:
  • “List the properties in my Abisko portfolio.”
  • “Show monthly emissions for [property name].”
  • “What certifications are active for [property]? Generate a CSV.”
  • “Plot monthly temperature and energy in a line chart from 2024 through 2026.”
Users can ask Claude to securely retrieve up-to-date data for property characteristics, building systems, performance, policies, capital projects, measures, certifications and more across their portfolio on-demand. Because each answer is a live lookup, results always reflect current data rather than a stale export or cached snapshot.
Abisko MCP enables users to leverage custom dashboards, reports and advanced agents and analysis that combine data from Abisko with other sources that can be accessed by their AI tools.

​
Advanced use cases

  • Capital Planning / Decarbonization Analysis: Generate a capital plan that fits your building and suggests the most appropriate measures based on your specific objectives.
    The plan integrates everything it knows about your building, including: property characteristics, location/climate, building systems, historical performance, suggested measures, regulatory exposure and more.
  • Resilience planning: Combine building systems and performance data with physical risk data for resiliency planning.
  • Due diligence: Integrate compliance, certification, and performance data into due diligence insights for investors.

​
Setup

Setup takes about a minute.
1

Open Settings → Connectors

In Claude Desktop, this may also appear as Customize → Connectors, depending on your version.
2

Select "+", then "Add custom connector"

This opens the form where you’ll name the connector and provide Abisko’s URL.
3

Name the connector "Abisko" and paste the connector URL

Contact Abisko to receive your connector URL.
Leave the Advanced section (OAuth Client ID and secret) empty.
4

Select "Add", then "Connect"

Sign in with your existing Abisko account, the same login you use on the platform today.
5

Start exploring and analyzing your Abisko data in Claude.

That’s it. Claude now looks up Abisko data whenever your question calls for it.
On a Team or Enterprise Claude plan? Your org admin may need to allow custom connectors before you can add one. This is controlled in Claude’s own admin settings, independent of Abisko.

​
How it works

​
Authentication

Connecting an Abisko account requires an interactive sign-in against Abisko’s own login, completed from inside the Claude client. Abisko does not issue shared service credentials or API keys for this flow, and no Client ID or secret configuration is needed on the Claude side. The resulting session is scoped to the signed-in user and carries their existing role-based permissions: the connector cannot see, query, or act on anything that user’s Abisko account could not already access. Disconnecting the connector at any time from Claude’s Connectors settings immediately ends the session, with no further action needed on the Abisko side.

​
Data scope: read-only

Every operation the connector exposes is a lookup. There is no write path: no operation creates, edits, or deletes Abisko data, changes settings, or triggers workflows.

​
What Abisko does not receive

Abisko has no visibility into your broader Claude session. It never receives the conversation itself, Claude’s memory, system prompts, or any content beyond the parameters of the specific lookup being made, such as which property or date range a query refers to. Abisko cannot see how a question was phrased or what Claude said in response.

​
Transport and hosting

All traffic between the Claude client and the Abisko connector endpoint is encrypted in transit over HTTPS/TLS. The endpoint is hosted and operated by Abisko under the same infrastructure and access controls as the core Abisko platform. No new data store or shadow copy of customer data is created for this integration: queries resolve live against production Abisko data.

​
Security summary