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 días gratis · sin tarjeta · hosting UE
Pregunta cualquier cosa a PlanRadar
Prueba un prompt real contra PlanRadar vía AnythingMCP — Claude llama a los tools y responde. Pulsa Enter en tu mensaje para instalar en Cloud.
Instalar PlanRadar en CloudClaude es IA y puede equivocarse. Verifica siempre las respuestas.
Setup en 2 minutos
- 1Inicia trial gratuita en cloud.anythingmcp.com.
- 2Click en PlanRadar en el connector store. Pega las credenciales.
- 3Genera MCP API key y apunta el cliente AI a la URL MCP.
Guías para PlanRadar
Setup paso a paso para los principales clientes AI.
Configurar PlanRadar
Directamente de la definición del conector: dónde encontrar las credenciales, qué permisos necesitan y con qué API habla este adaptador. Proporcionadas en inglés por el autor del conector.
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.
Tu IA está a dos clicks de PlanRadar.
Instala el conector, pega credenciales, pregunta a la IA. 7 días gratis, sin tarjeta.