---
name: equire-mcp
description: Use when connecting an approved EQUIRE organization to its OAuth-protected MCP deal-intelligence connector.
---

# EQUIRE MCP connector

Use this skill when a user needs source-grounded commercial-real-estate deal intelligence from an approved EQUIRE organization. The connector is OAuth-protected. It does not provide anonymous access, a public sandbox, or authority to approve investment decisions.

## Discover the contract

1. Read the [MCP server card](https://www.equire.ai/.well-known/mcp/server-card.json) for the current endpoint, registered tools, and required scopes.
2. Read the [authentication guide](https://www.equire.ai/auth.md) before creating a client or requesting access.
3. Use the [OpenAPI description](https://www.equire.ai/openapi.json) and [developer guide](https://www.equire.ai/developers) for protocol details and error behavior.

## Connect safely

1. Use OAuth authorization code with PKCE S256 and an allowlisted redirect URI.
2. Request only the scopes required for the task. Write and staged-action scopes are not granted by default.
3. Treat every response as organization-scoped, permission-aware, and source-grounded. Ask for missing scopes rather than retrying around a denial.

## Governed actions

Use read tools to inspect deal evidence, diligence, valuation context, and review state. Write tools require an active EQUIRE role, an explicit write scope, idempotency protection, and an audit trail. Staged actions remain proposals for EQUIRE review; never present them as applied or approved decisions.