PlanRadar and AI: Is there an MCP server for PlanRadar?

PlanRadar from PlanRadar GmbH in Vienna is, according to its terms, software for construction documentation and defect management. If you want an AI assistant such as Claude or ChatGPT to work with PlanRadar data, the first question is: is there an MCP server for it?

In short

We found no MCP server from PlanRadar. PlanRadar offers a REST API (Pro and Enterprise only) and its own AI features. To connect an external assistant, you need an MCP server that uses this API. The open-source toolkit AnythingMCP ships a connector for it.

What PlanRadar offers itself

MCP. We found no MCP server and no announcement about one at PlanRadar. A search in the PlanRadar help centre for MCP and for Model Context Protocol returns no results. The sitemap of planradar.com contains no URL with MCP. A Cloudflare check kept us from reading planradar.ai, which planradar.com links to.

The REST API. According to the help centre, PlanRadar provides REST APIs for customers’ own integrations. They return JSON. Sign-in uses a personal access token in the header X-PlanRadar-API-Key. The help centre says the Open API is only available for Pro and Enterprise accounts. An in-house user also needs the permission API Access. According to Core API Concepts, 30 requests per minute apply per account. Exceeding the limit triggers a five-minute cooldown. PlanRadar says it is upgrading the APIs to v2 and recommends v2 where it exists. With PlanRadar Connect, PlanRadar links third-party systems without coding. According to PlanRadar, Connect is built on Workato. The page does not mention MCP.

AI assistant. According to PlanRadar, the assistant helps to find tickets and documents, summarise documents, analyse tickets and create ticket filters. It also answers how-to questions. It always works in one project, only with the user’s rights and only with text-based files. It does not analyse photos. Plans are the exception: “Ask AI” on a plan answers questions about what is drawn on it. According to PlanRadar, it does not create, edit or delete tickets or documents. The advanced features need the permission AI access and are not available to subcontractors and watchers.

AI agents. According to PlanRadar, agents react to events in a project, such as a new or updated ticket, a comment or a new file. They may create tickets, write comments and send emails to project members. Creating them needs an in-house user with the permissions AI access and AI Agents. They run with the rights of their owner. According to PlanRadar, they do not change or delete existing tickets, documents or plans. You can create agents only in the web app.

Usage limit. According to PlanRadar, all users of an account share one AI usage limit. It does not reset by itself. After that, the AI features are blocked except for how-to questions, until the account requests and receives “AI Plus”. The pricing page lists “AI workflow features included” with the note “Shared workspace usage limits apply”. According to the help centre, the AI features are available on all plans (Basic, Starter, Pro, Enterprise), and the usage limit applies to all.

Data processing. According to PlanRadar, the AI features use Amazon Bedrock in the existing AWS environment in the region eu-central-1 (Frankfurt). According to PlanRadar, customer data goes to no model provider, and neither AWS nor a model provider trains models with it. PlanRadar stores chat history under its standard retention policy and, by its own account, uses it to improve the user experience and to understand how users use the AI features. You can switch the AI off only for the whole account, on request to support.

Data region. According to PlanRadar, operational and customer data is stored on servers in Germany at AWS. The help page on the AI assistant instead names AWS accounts in the EU, the US or the UK. We found no source on which region a customer gets or can choose for an account. So we set no value for the data region.

What the community offers

We found no dedicated PlanRadar MCP server on GitHub. The hits for “planradar” are mostly job assessment tasks and private projects. At the Zapier addresses we checked (zapier.com/apps/planradar), we got a 404 error. The viaSocket address for PlanRadar shows only the general overview. This does not prove that no integration exists there. Make’s page blocked us with a Cloudflare check, so it stays unread. The Glama directory shows no PlanRadar match.

AnythingMCP is a general open-source gateway (AGPL-3.0). It includes a PlanRadar connector with 10 tools: read projects, tickets, users and documents, create and update tickets. It uses the PlanRadar API v1 with an API key and customer ID. According to the vendor, self-hosting is free up to 3 active users. According to AnythingMCP, there is also a hosted cloud in Frankfurt with a 7-day trial. The API limit of 30 requests per minute applies here too. We did not test the connector.

What this means for your company

• Check your plan first. According to PlanRadar, the Open API exists only in Pro and Enterprise.
• An MCP connector for Claude or ChatGPT uses an API token. Create a dedicated user with the rights it needs.
• A connector with write tools can create and change tickets. If possible, use read-only tools.
• Ask PlanRadar for the data region of your account before you pass data to an AI assistant outside PlanRadar.
• What reaches the external AI assistant falls under its terms, no longer under PlanRadar’s.