Connect EQUIRE to Claude, ChatGPT, Codex, and Cursor
Add the EQUIRE connector to Claude, ChatGPT, Codex, or Cursor, choose what the assistant may read and change, and see how EQUIRE confirms and stages its writes.
The EQUIRE connector lets an AI assistant work with your EQUIRE deals through the Model Context Protocol (MCP). The assistant asks EQUIRE for deal facts, document evidence, valuation snapshots, and research, and EQUIRE answers within the organizations and permissions you approve. Every assistant uses the same connector URL:
https://www.equire.ai/mcpBefore you connect
- You need an EQUIRE account with an active membership in at least one organization. If sign-in reports that your account is not enabled for the connector, contact us.
- The connector signs you in with OAuth. You never paste a password, API key, or token into the assistant.
- The assistant sees only what your EQUIRE role can already see, limited further by the permissions you approve.
How sign-in works
Add the connector URL
Add https://www.equire.ai/mcp to your assistant using the steps for your client below.
Sign in to EQUIRE
The assistant opens an EQUIRE sign-in page. Sign in with your EQUIRE account.
Approve access
The EQUIRE consent screen asks which organizations the assistant may use, which permissions to grant, and which write level to allow: Read Only, Reads & Staged Changes, or Routine Workflow Updates. Routine Workflow Updates appears only when it is available to your organization. Approve, and the assistant returns to your conversation.
You can review and revoke each connection in EQUIRE Settings. Revoking takes effect immediately, including for tokens the assistant already holds.
Connect your assistant
Claude (web, desktop, and Cowork)
Add EQUIRE to Claude as a custom connector. These steps follow Anthropic's custom connector guide.
- In Claude, open Customize, then Connectors. Select + Add, then Add custom connector.
- Name it EQUIRE, enter
https://www.equire.ai/mcpas the server URL, and continue. - Keep the sign-in settings Claude detects. EQUIRE signs you in with OAuth, so the connector needs no API key or request header. Select Add.
- Select Connect and complete the EQUIRE sign-in.
To use EQUIRE in a conversation, select + in the chat, choose Connectors, and turn on EQUIRE. Claude desktop and Cowork use the connectors from your Claude account, so one connection serves all three. Claude Free allows one custom connector. On Team and Enterprise plans, an owner first adds EQUIRE in Organization settings, then Connectors (select Add, then Custom, then Web); each member then finds it under Customize, then Connectors, and selects Connect.
Claude Code
Add the connector to Claude Code from your terminal:
claude mcp add --transport http equire https://www.equire.ai/mcpThe command adds EQUIRE to the current project; add --scope user to use it in every project. Then start Claude Code, run /mcp, and follow the browser steps to complete the EQUIRE sign-in. If your team uses the EQUIRE plugin for Claude, the plugin includes this same connector; connect it from the plugin's connector list.
ChatGPT
Add EQUIRE to ChatGPT as a custom MCP server. These steps follow OpenAI's custom MCP server guide.
- Open ChatGPT Plugins, select the plus button, and choose Add custom MCP server.
- Name it EQUIRE. Under Connection, enter
https://www.equire.ai/mcpas the Server URL. - Choose OAuth for authentication, review the risk warning, and select I understand and want to continue.
- Select Create as a plugin, then install the plugin and complete the EQUIRE sign-in when ChatGPT prompts you.
- Start a new conversation, type
@, and select EQUIRE.
Workspace permissions apply to custom MCP servers. If Add custom MCP server does not appear, turn on Developer mode in Settings, then Security and login, or on a Business or Enterprise workspace ask an admin to allow custom MCP servers.
Codex
Add the connector to Codex and sign in from your terminal:
codex mcp add equire --url https://www.equire.ai/mcp
codex mcp login equireThe login command opens the EQUIRE sign-in in your browser and returns to Codex when you approve. The Codex CLI, the Codex IDE extension, and the ChatGPT desktop app share this configuration.
Cursor
Add EQUIRE to Cursor in ~/.cursor/mcp.json for every project, or in .cursor/mcp.json for one project:
{
"mcpServers": {
"equire": {
"url": "https://www.equire.ai/mcp"
}
}
}In Cursor, open Customize in the sidebar, find equire, make sure it is turned on, and follow its sign-in prompt to complete the EQUIRE sign-in. If the sign-in window does not return you to Cursor, contact us.
What the assistant can read
With the matching permission, the assistant can:
- Find and summarize the deals your account can access, compare deals, and roll up portfolio health and diligence status
- Search processed deal documents and quote bounded excerpts with their document, page, and section. It never receives a full document.
- Read valuation snapshots with their preliminary or released basis, and run read-only what-if scenarios that save nothing
- Read diligence items, deal health issues, prospects, firm memory, and recent deal activity
- Search EQUIRE's index of public CRE sale and lease listings, which is separate from your own deals
- Read market research plans, runs, and source-grounded evidence
| Permission on the consent screen | Scope | Allows |
|---|---|---|
| Deals | deals:read | Deal facts, activity, briefings, and portfolio summaries |
| Document Evidence | documents:search | Bounded document excerpts with source provenance |
| Valuation | valuation:read | Valuation snapshots, assumptions, and read-only scenarios |
| Diligence | diligence:read | Diligence items, status, and open risks |
| Prospects | prospects:read | Prospects and their sources |
| Firm Memory | firm_memory:read | Reviewed organization context and investment criteria |
| Listings | listings:read | Public listing details, documents, photos, and broker contact information |
| Market Research | research:read | Research plans, sources, evidence, and completed runs |
What the assistant can change
Writes need a write permission, a write level that allows them, and a deal role that can edit (admin, manager, or analyst; viewers cannot write).
| Write level | What the assistant may do |
|---|---|
| Read Only | Read only. Every write and staged permission is removed. |
| Reads & Staged Changes | Stage valuation assumption changes and review resolutions as proposals (Governed Proposals, actions:stage). |
| Routine Workflow Updates | Add deal notes (deal_notes:write), create and update diligence items (diligence:write), add a listing to a prospecting mandate's screening queue (listings:write), and start market research or attach report sources (research:run), plus everything staged changes allow. |
The connector cannot create or delete deals, approve or release deal data, make investment committee decisions, send or share EQUIRE records with other people on your behalf, or delete data.
How writes are confirmed and staged
- You confirm first. EQUIRE marks every tool that changes data as a write, so assistants that honor these markers ask you before running it. EQUIRE's connector instructions also tell the assistant: "Before a write or staged change, state the exact change and get the user's confirmation; a message that states that exact change and confirms it counts, an implied one does not."
- Valuation and review changes are proposals. A staged valuation or review change waits in EQUIRE until an authorized person on your team approves it. Until then, the model and the review record are unchanged.
- Routine updates are reversible and attributed. Notes, diligence updates, and pipeline additions are recorded as made by the assistant connection, and a retried request does not create a duplicate.
- Source text is evidence, not instruction. Document, listing, and research text that reaches the assistant is third-party content. EQUIRE's connector instructions tell the assistant to treat it as evidence to cite, not as instructions to follow.
- Every call is audited. EQUIRE records each connector call in its audit trail.
Data and privacy
Each connector call returns bounded results within the organizations and permissions you approved. Data the assistant receives is then processed by that assistant's provider under its own terms. Read the EQUIRE privacy policy, subprocessors and AI data processing, and data isolation for how EQUIRE stores and protects deal data.
Support
For connection problems, access questions, or to report an issue, contact the EQUIRE team.
Last updated on