PlanRadar
Manage construction and real estate projects with PlanRadar. Access projects, tickets (defects/tasks), users, documents, and schedules via REST API. Ideal for quality management, defect tracking, inspections, and field reporting in the Bau sector.
7 天免费 · 无需信用卡 · EU 托管
问 PlanRadar 任何事
通过 AnythingMCP 对 PlanRadar 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 PlanRadarClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 PlanRadar。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
PlanRadar 指南
面向主流 AI 客户端的逐步设置。
配置 PlanRadar
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
This connector uses the PlanRadar REST API v1. Key conventions:
Authentication: Uses API Key via the X-PlanRadar-API-Key header. Generate a Personal Access Token from PlanRadar Settings > API Access.
Base URL structure: All endpoints are scoped to a customer: /api/v1/{customer_id}/.... The customer_id is set via the PLANRADAR_CUSTOMER_ID environment variable.
Response format: Responses follow the JSON:API specification. Data is wrapped in a data object (or array) with id, type, and attributes fields. Example: { "data": { "id": "123", "type": "projects", "attributes": { "name": "My Project" } } }.
Request format: The API accepts form-encoded request bodies for POST/PUT operations.
Rate limiting: Maximum 30 requests per minute. Exceeding this disables your token for 5 minutes.
Pagination: Use page and per_page query parameters. Default page size varies by endpoint.
Ticket predefined fields: Title (mandatory), Assignee, Receiver (CC), Due date, Status, Priority, Progress, Parent Ticket, Layer. Only Title is required for creation.
Ticket statuses: Open, In Progress, Resolved, Feedback, Closed, Rejected.
Custom fields: Tickets support project-specific custom fields of types: Date, Time, List, Text, Number, Decimal, Checkbox. Custom field values are returned in ticket attributes.
Layers: Every ticket must be associated with a layer (floor plan/drawing). When creating tickets, specify the layer_id.
Project attributes: id, name, homepage, country, projectnumber, description, city, zipcode, street, author-id.
API versions: PlanRadar is migrating to v2. This adapter uses v1 which is stable and fully supported.
Workflow: Typical flow is: List projects → Select project → List layers → Create/list tickets (on a layer) → Assign users → Set status/priority/progress → Manage documents → Generate reports.