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 Tage gratis · keine Kreditkarte · EU-Hosting
Frag PlanRadar alles
Teste einen echten Prompt gegen PlanRadar via AnythingMCP — Claude ruft die Tools auf, liefert die Antwort. Drück Enter auf deine eigene Nachricht, um auf Cloud zu installieren.
PlanRadar auf Cloud installierenClaude ist KI und kann Fehler machen. Bitte Antworten gegenprüfen.
Setup in 2 Minuten
- 1Free Trial auf cloud.anythingmcp.com starten.
- 2Im Connector-Store auf PlanRadar klicken. Credentials einfügen.
- 3MCP-API-Key generieren und KI-Client auf die MCP-URL zeigen.
Anleitungen für PlanRadar
Schritt-für-Schritt-Setup für die wichtigsten KI-Clients.
PlanRadar einrichten
Direkt aus der Connector-Definition: wo du die Credentials findest, welche Rechte sie brauchen und mit welcher API dieser Adapter spricht. Vom Connector-Autor auf Englisch bereitgestellt.
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.
Deine KI ist zwei Klicks von PlanRadar entfernt.
Connector installieren, Credentials einfügen, KI fragen. 7 Tage gratis, keine Kreditkarte.