CupixCompass MCP Server

Explore and analyze Cupix construction site data: 360 images, progress, and insights.

Tools

Last Updated

Jun 14, 2026

What is the CupixCompass MCP Server?

The CupixCompass MCP server gives AI agents structured, permission-aware access to CupixCompass through the Model Context Protocol. With 6 pre-built actions, agents can read, create, and update CupixCompass data on behalf of authorized users.

Willow ships the CupixCompass MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how CupixCompass is being used by every AI agent in your stack.

Tools

compass_list_projects

List construction projects the user can access within a team. **Use this tool ONLY when the user wants to switch project or has no saved current project.** If `compass_get_current_project` returns a saved facility_key, do NOT call this tool — call the analysis tool directly with no arguments. Required workflow when this tool IS appropriate: 1. Present the returned projects to the user. 2. Wait for the user to select one. 3. Call `compass_select_project(team_domain, facility_key)` to persist the selection so future sessions skip this step. 4. Then invoke analysis tools. Args: team_domain: Team domain. Optional; if omitted, falls back to the saved current project, otherwise returns the team list so the caller can pick a team first. Returns: str: Accessible facilities with their keys and names.

compass_query_database

Query the construction project database using natural language (Text-to-SQL). Converts natural language into SQL to retrieve captures, annotations, progress metrics, schedules, and other project records. Pass the user's question as-is without modification. For trade visibility, use compass_analyze_work_in_place instead. **WORKFLOW:** - **Default**: call this tool with only `query`. The server resolves team_domain/facility_key from the saved current project (set via `compass_select_project`). Do NOT call `compass_list_projects` again just to obtain these values. - Only when the response indicates the current project is missing, run `compass_list_projects` → ask the user → `compass_select_project`, then retry. - Pass explicit team_domain/facility_key **only** when the user clearly wants to query a different project than the saved one. **Available tables:** - progresses: SI progress metrics (level, category, phase, workarea, cost, dates) - captures: Camera captures metadata (level, camera_model, capture_state, user_email) - records: Capture events with timestamps (captured_at, state, id) - photo_notes: Photonotes (description, state, user_email, created_at) - voice_notes: Voicenotes (level, description, state, user_email, created_at) - facilities: Site info (name, address, size, location, bim_count, created_at) - users: User profiles (name, email) - workareas: Spatial zones (level, name, user_name) Args: query: Natural language question (pass as-is, no SQL syntax) team_domain: Omit by default. Pass only to override the current project. facility_key: Omit by default. Pass only to override the current project. Returns: Query results as tab-separated text

compass_select_project

Save the user's current team and project so subsequent tool calls can omit the `team_domain` / `facility_key` arguments. Args: team_domain: Team domain to remember (required unless `clear=True`). facility_key: Facility key to remember (required unless `clear=True`). clear: If true, delete the stored selection and ignore the other args. Returns: Human-readable confirmation message.

compass_get_current_project

Return the currently saved team_domain and facility_key for this user.

compass_search_360_captures

Search 360° captures (panoramic site photos) by visual content analysis. Searches what is VISUALLY SEEN in 360° captures — safety hazards, quality issues, work types, objects, equipment, materials, and physical site conditions. Do NOT use for capture counts or statistics — use compass_query_database instead. **WORKFLOW:** - **Default**: call this tool with only `query` (and optionally date filters / limit). The server resolves team_domain/facility_key from the saved current project (set via `compass_select_project`). Do NOT call `compass_list_projects` again just to obtain these values. - Only when the response indicates the current project is missing, run `compass_list_projects` → ask the user → `compass_select_project`, then retry. - Pass explicit team_domain/facility_key **only** when the user clearly wants to search a different project than the saved one. **Date filtering:** Only use start_date/end_date when the user explicitly mentions dates. Format: YYYY-MM-DD. Omit entirely for general queries without date context. Args: query: Keywords or phrases describing what to find in 360° captures team_domain: Omit by default. Pass only to override the current project. facility_key: Omit by default. Pass only to override the current project. limit: Maximum number of results (default: 10) start_date: Start date filter, YYYY-MM-DD (omit if no date context) end_date: End date filter, YYYY-MM-DD (omit if no date context) Returns: ToolResult: Image viewer links, 3D coordinates, and capture dates

compass_analyze_work_in_place

Analyze Work In Place (WIP) progress from SiteInsights(SI) — completion rates, delays, and forecasts. Generates a progress report: overall completion, progress by category/vendor/level, delay analysis, and estimated completion dates. **WORKFLOW:** - **Default**: call this tool with NO arguments. The server resolves team_domain/facility_key from the saved current project (set via `compass_select_project`). Do NOT call `compass_list_projects` again just to obtain these values — the saved selection is the source of truth. - Only when the response indicates the current project is missing, run `compass_list_projects` → ask the user → `compass_select_project`, then retry. - Pass explicit arguments **only** when the user clearly wants to analyze a different project than the saved one. Args: team_domain: Omit by default. Pass only to override the current project. facility_key: Omit by default. Pass only to override the current project. Returns: Progress analysis report with completion rates and forecasts

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your CupixCompass MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-cupixcompass": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/cupixcompass"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-cupixcompass": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/cupixcompass"
    }
  }
}

Claude Code

CLI

claude mcp add willow-cupixcompass --transport http https://<org>.mcp-s.com/mcp/mcp/cupixcompass

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/cupixcompass",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for CupixCompass

Willow adds the layer CupixCompass and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

CupixCompass MCP Server FAQ

What is the CupixCompass MCP server?

The CupixCompass MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write CupixCompass data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's CupixCompass MCP server different from the official one?

The official CupixCompass MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the CupixCompass MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the CupixCompass MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in CupixCompass, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which CupixCompass actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow CupixCompass MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved CupixCompass MCP locally, you'll see it.

What does the CupixCompass MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the CupixCompass MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.