Placepoint AI

Placepoint AI makes Placepoint available in Claude: in Claude Desktop, Claude Code and Cowork. Two MCP servers give Claude all of Placepoint, both data and features, and you write what you want to know in the language you use yourself.

Claude retrieves Placepoint's combined, contextualised and quality-checked data (matrikkel (the Norwegian property register), Grunnboken (the land register), company data, map layers and more, see Data and sources), combines it with open sources and your own datasets, and puts it all together into an answer, a table, a map, an interactive dashboard or a PDF report of the same type as the reports in Placepoint Fusion.

There are two servers. Placepoint MCP gives Claude the registers and the map layers. Placepoint Dataset MCP gives Claude your projects and datasets in Placepoint Fusion, so the result of an analysis can become a map layer you keep working on, and your lists can meet the registers in the same question. See Two servers, one conversation.

ℹ️ Placepoint AI is under rapid development. New tools and data sources arrive continuously, and features, data and access can change along the way. Verify the results against official sources before they are used for decisions.

What is MCP

MCP (Model Context Protocol) is an open standard for giving an AI assistant access to tools and data sources, and it is used by Claude and a range of other AI tools. When Placepoint AI is connected in Claude, Claude can look things up in our property registers while the two of you talk, instead of guessing from what the model remembers. You do not need to know anything about matrikkel structure, field names or APIs. You ask, Claude retrieves.

The foundation is the same as in Placepoint: around 2,300 data sources and map layers from public agencies, kommuner and commercial vendors, covering 3.5 million matrikkelenheter (cadastral units), 1.1 million active companies and more than 30 million ownership relationships between companies, owners and property. Each individual dataset, what it contains and where you find it at the source, is listed under Data and sources. The scope in numbers is on Placepoint in numbers.

Two servers, one conversation

	Placepoint MCP	Placepoint Dataset MCP
What Claude gets	The registers and the map layers: matrikkel, Grunnboken, companies, land-use plans, risk, travel time	Your projects and datasets in Placepoint Fusion
Direction	Reads. Nothing you ask changes anything in Placepoint	Reads and writes. Claude can create datasets, add rows and columns, and change the style of the map layer
Typical question	"Who owns [address], and what is registered on the property?"	"Upload our tenant list, link it to the matrikkel and show it on the map."
The result	An answer, table, map, dashboard or PDF report in Claude	A dataset in your project, visible and editable in the map
Sign-in	Your Placepoint user. You get the URL for the server from your contact at Placepoint	Your Placepoint user. Access follows the projects you have access to

Together they cover the workflow from question to delivery. Claude finds the properties with Placepoint MCP, and saves the result as a dataset with Placepoint Dataset MCP. The next time you open the project in Placepoint Fusion, the list is there as a map layer. In the other direction, you upload your own list, a portfolio, a customer list or a tenant register, and ask about it together with the registers: which properties on the list have a new owner or a new charge since last time?

From days to minutes

Much of the most important analysis work around property is still manual: finding the right register, extracting the data, quality-checking it and putting it all together into something the board, the credit committee or the client can read. It takes days or weeks, often requires an external consultancy, or never gets done because it is too extensive to be prioritised.

With Placepoint AI, Claude does the same work in minutes, and delivers the result as a report, an interactive dashboard or a presentation. Examples of work that today ties up skilled people for days:

• Property companies and managers: portfolio and board reports across SPV structures, tenant overview per building with how long each tenant has been registered, ESG status for the entire portfolio.
• Law firms: due diligence with a review of encumbrances (charges, easements, rights of way and subdivision bans) for many properties at once, and mapping of ownership chains from the ultimate owner down to each individual company.
• Brokers and advisers: source material for sales prospectuses and valuations, buyer assessment of a counterparty, location analyses for chains and businesses.
• Banking and insurance: climate risk and nature risk per property or portfolio (flooding, landslides, quick clay, surface water), and credit assessments with traffic lights per risk topic.

And you do not need to look up one property at a time. Ask about a whole street, a block or a district, and Claude does the job for all the properties in the area at once. The prompt "Check the whole of John Colletts allé, where can new buildings go, produce a report" gave a 15-page report that went through all 72 land parcels in the street, with a map and an assessment per address. Along the way, Claude read the plan documents themselves, and found four addresses in the middle of the street that are not covered by the building ban that stops all the neighbours. That exemption is not in any map database. It is in the decision on the extended building ban, because the requirements are in the planning provisions, not in the colours on the plan map. Going through 72 properties and their plan documents by hand is days of work; here it took minutes.

The foundation is the data Placepoint has already collected, quality-checked and put in context: see Data and sources. Claude retrieves from that same foundation, so you avoid searching each individual source and stitching it together yourself.

What you can do with Placepoint AI

The examples below are finished reports and analyses our users have already produced with Placepoint AI. Replace the placeholders in square brackets with a real address, a matrikkelnummer (cadastral number) or a company registration number:

• Look up [address] or [matrikkelnummer] and gather facts about the site, buildings, units, owners and tenants in one place, the way the property panel and the units and tenants tab do it in Placepoint Fusion.
• Search and filter properties on criteria across the whole of Norway, for example year of construction, building type, area or tenants, and export the result.
• Retrieve the full land register extract for [matrikkelnummer] and summarise the encumbrances: charges, easements, rights of way and subdivision bans.
• Bulk-scan Grunnboken records and encumbrances for a whole area at once, for example all matrikkelnummer within [area].
• Map the companies behind [matrikkelnummer]: ownership structure from the ultimate owner down to the subsidiaries, roles, shareholders and annual accounts, as in the company panel.
• Produce a due diligence report for [matrikkelnummer] with a legal, technical and financial review.
• Produce a credit and risk report for [matrikkelnummer].
• Produce a climate risk and nature risk report for [matrikkelnummer] for use in a credit assessment, with traffic lights (red, amber, green) per topic such as flooding, landslides, quick clay, surface water, cultural heritage and threatened species.
• Produce a climate risk and sustainability analysis for a head office at [address], with tenants, certification and travel time.
• Check the risk and the framework around [matrikkelnummer]: flooding, landslides, quick clay, zoning and municipality plans, habitat types and protected areas, shown on a map with the risk map layers.
• Find out which land-use plans apply to [matrikkelnummer], including municipality plan proposals, and get the plan map shown together with the property boundaries, in line with the zoning map layers.
• Retrieve the plan documents for a plan, for example the planning provisions and the plan description, and have them read and summarised, not just listed.
• Search for land-use plans in an area or by plan name, and see plan maps and plan proposals alongside what has been adopted, including detailed zoning plans and area zoning plans.
• Retrieve historical aerial photos around [matrikkelnummer] and compare the area year by year.
• Calculate travel time and reach by car, public transport, bicycle or on foot, and find properties within a given travel time.
• Do a location analysis: the best place for a new shop in [area], or suitable sites for data centres in Norway.
• Produce an investment and development analysis for [matrikkelnummer]: demolish or extend, yield, development density, development potential and possible land use.
• Produce a buyer assessment of [company registration number] that wants to take over [matrikkelnummer].
• Retrieve the full property portfolio of [company], including properties owned indirectly through subsidiaries and SPV chains.
• Produce a portfolio or board report for [company registration number], of the same type as the reports in Placepoint Fusion.

With Placepoint Dataset MCP in addition:

• Save a search result as a dataset in your project, for example all logistics properties over 10,000 m² in [municipality] with owner and year of construction, and get it as a map layer in Placepoint Fusion.
• Upload an Excel file and have the rows linked to the matrikkel by address or matrikkelnummer, the way dataset upload does it in the platform. If you have the geometry in GeoJSON or WKT, put it in a column in the spreadsheet.
• Add municipality, grunnkrets (basic statistical unit) or postcode as columns in a dataset, and sum or count rows per area.
• Ask about your own rows together with the registers: which properties in [dataset] have changed owner, received a new charge or lie in a flood zone?
• Calculate travel time from each point in a dataset, or find the shortest route that visits them all.
• Tidy up a dataset: change values, add columns, hide columns and set colours and symbols on the map layer.

Finished reports, with a complete report example to download, and short example prompts you can start with, are on Examples.

How reports are delivered

Reports are delivered as HTML by default, because that is fastest and lets you read the result straight away. Ask for PDF when you need a document to send on, and choose between one long page or genuinely paginated pages. PDF takes longer to produce, and Claude tells you how long it will take before it starts.

When a plan is discussed in a report or analysis, Claude reads the planning provisions and the plan description first, instead of building the text on the plan name alone. Property lookups also suggest plan status and a hazard sweep (landslides, flooding, quick clay and similar) as the next step, so zoning and risk are not skipped. The reports resemble the ones you produce in Analyses and reports.

Which data is available

Claude retrieves from the same sources that underpin Placepoint:

• The matrikkel: properties, buildings, units, area and year of construction for the whole of Norway, as in the property panel and the building panel.
• Grunnboken: title history and registered encumbrances, with a full land register extract on request.
• Company data: roles, ownership, the shareholder register and annual accounts from Brønnøysundregistrene (BRREG) and related sources, equivalent to the company panel.
• Transactions: registered changes of ownership and sales, including company sales.
• Map layers: around 2,300 sub-layers spread over around 170 map services from, among others, Norges vassdrags- og energidirektorat (NVE), Norges geologiske undersøkelse (NGU), Miljødirektoratet, DIBK, Geodata AS and Placepoint. Covers, among other things, flooding, landslides, quick clay, zoning and municipality plans, habitat types and protected areas, energy labelling, demographics, public transport coverage and emergency preparedness.
• Land-use plans: five datasets covering adopted zoning plans, plan proposals under consideration, the municipality plan, municipality plan proposals and notices of plan initiation, including Oslo. With plan maps and plan documents (planning provisions, plan description and more) as PDF, which Claude reads where they exist. Lookups per property use the property's actual boundaries, not just a point, so the matches are more accurate. If plan data is missing for a property, Claude says so instead of describing the property as unzoned. The same plans are in the zoning map layers.
• Travel time and traffic: routes, isochrones and travel time matrices with up to 100 × 100 points, the same basis as Travel distance in Analyses.
• Aerial photos: historical and current images from Norge i bilder.

In total, Claude retrieves from more than 130 datasets delivered by around 25 organisations. Most are open, public sources, among them Kartverket, Brønnøysundregistrene, NVE, NGU, Miljødirektoratet, DIBK, Artsdatabanken, Statistisk sentralbyrå (SSB) and Statens vegvesen. In addition come commercial vendors and services, among them Geodata, Microsoft Azure Maps (background maps and places) and TravelTime (travel time).

You will find an overview on Data and sources, and who delivers what on Vendors.

Can be combined with other systems

Placepoint AI is not meant to replace the specialist systems you already use, but to work alongside them. The property data Claude retrieves can be combined with information from other solutions, for example systems for physical property management (leases, areas, operation and maintenance), ERP and finance systems, and specialist systems for the management, operation and maintenance of public building stock. Then you can use Placepoint for matrikkel, Grunnboken, company and risk data, and your own systems for what they are best at, in the same analysis or report.

In Claude Desktop, in Cowork and in Claude Code you connect to other MCP servers yourself, alongside Placepoint's. In the Agent in Placepoint Fusion, the administrator sets up the connections to external systems; which systems are ready and which are coming is described on Placepoint Agent.

The Agent in Placepoint Fusion

Placepoint AI is also available inside Placepoint Fusion, as the Agent, in pilot. There you ask the same questions directly in the platform, without Claude Desktop, Cowork or Claude Code. The Agent uses both MCP servers, controls ordinary Fusion features such as the map, the map layers and the property panel, searches this user documentation when you wonder how something is done, and can be connected to other systems the business uses. The Agent is being trialled with selected users. It produces neither images nor files, so historical aerial photos, density maps and export to spreadsheets are only available in Claude; in the Agent the answer comes as text and map links.

Personal data is not available

Placepoint AI does not give out information about private individuals. When Claude retrieves a land register extract, personal names and national identity numbers are removed automatically before the data reaches the model, and private individuals are shown as Private person. So you cannot use Placepoint AI to find out who owns a home, or to look up individuals. Companies, roles and ownership structure are open data and are included.

This applies regardless of which access level your account has elsewhere in Placepoint. The extended access to personal data that some professional users can get in the platform itself (documented "legitimate interest") does not apply to Placepoint AI.

Placepoint Dataset MCP works with your own datasets, and only sees the projects your Placepoint user has access to. The content of the files you upload is your responsibility in the same way as when you upload them in the platform.

How to get started

We work closely with property companies, law firms, brokerages, banks and insurance companies, and what they need steers what gets built next.

If you want to take part, get in touch via placepoint.no/selskap/kontakt.

How to install

Both servers are added as a "Custom MCP", a separate MCP server, and they work everywhere Claude accepts your own MCP servers: in Claude Desktop, in Claude on the web, in Cowork and in Claude Code. The same URL and the same sign-in wherever you connect.

In Claude Desktop, in Claude on the web and in Cowork, the procedure is described in Get started with custom connectors using remote MCP. It is the same for both servers: add the URL you get from your contact at Placepoint, click Connect and sign in with your Placepoint user. You sign in once per server, with the same user you use in Placepoint Fusion.

In Claude Code you add the server from the terminal and sign in with /mcp:

claude mcp add --transport http placepoint <URL-en fra Placepoint>

• Placepoint MCP: the registers and the map layers. Access follows your user, not the URL.
• Placepoint Dataset MCP: your projects and datasets. Claude sees the same projects and datasets that you see in Placepoint Fusion.

If new tools are missing from the list, go to Settings, Customize, Connectors, select Placepoint, click the three dots and select Refresh tools list. Take questions, missing access and feedback up with your contact at Placepoint.

Updates

New tools do not appear until the connector has been updated. If they are missing in Claude, go to Settings, Customize, Connectors, select Placepoint, click the three dots and select Refresh tools list.

03/09/2026:

• Sign-in with your Placepoint user on both servers. You click Connect in Claude and sign in the way you do in Placepoint Fusion. Access follows the user instead of the URL.

02/09/2026:

• Placepoint Dataset MCP: a separate server for your projects and datasets in Placepoint Fusion. Claude can create datasets from a search result, upload and matrikkel-link files, add municipality and grunnkrets as columns, sum per area, calculate travel time and optimise routes, and set the style of the map layer. You sign in with your Placepoint user, and access follows your projects.

19/08/2026:

• Land-use and zoning plans now cover five datasets: adopted zoning plans, plan proposals under consideration, the municipality plan, municipality plan proposals and notices of plan initiation. Oslo is included. The MCP finds the plan documents themselves, so Claude can read the planning provisions where they exist, and it is in the provisions that the requirements actually sit, not in the colours on the plan map.
• Pilot of Placepoint AI inside Placepoint Fusion, as the Agent: the same tools and data sources, ordinary Fusion features and search in the user documentation.

11/08/2026:

• New land-use plan suite: search in land-use plans, retrieve plan details with the plan map, see which plans apply to a property, and retrieve plan documents (planning provisions, plan description and more) as PDF. Equivalent to the zoning map layers in Placepoint Fusion.
• The plan check per property only needs the matrikkelnummer. The property's actual boundaries are retrieved automatically and used in the lookup, which gives more accurate matches than before. Municipality plan proposals are included as a separate category.
• Plan documents are read, not just listed. If a plan is to be discussed in a report or analysis, Claude checks that the provisions and the plan description have actually been read first. If plan data is missing for a property, this is stated explicitly in the delivery instead of the property appearing to be unzoned.
• Property lookups suggest plan status and a hazard sweep (landslides, flooding, quick clay and similar) as the next step, so zoning and risk are not skipped.
• Reports are delivered as HTML by default, which is considerably faster. PDF is produced on request, with a choice between one long page or genuinely paginated pages, and a note about how long it takes before the heavier variant is run.
• The map tools give better error messages: unknown map layers give a message with valid alternatives, large geometries are simplified in a controlled way with a clear note, and geometries can be reused between tools without being pasted in again.
• The usage guide and the tool descriptions have been expanded, so that Claude chooses the right tool for plan and zoning questions.

Caveats

• Placepoint AI is under active development. Some tools and map layers are not fully tested and can fail.
• Both servers require sign-in with your Placepoint user. Access follows the user, so it cannot be lent out by sharing a URL.
• Claude can be wrong. The results are a starting point, not a final answer, and must be verified against official sources before they are used for decisions.
• Access, features and data can change along the way.