Skip to main content
Loss of provenance

A previous release had provenance metadata, but this release does not. View details.

How to connect Crexi to Claude Code, ChatGPT and any AI agent

Yes, Claude, ChatGPT and other AI agents can work in your Crexi account. Crexi's Listing API is only for MLSs and large brokerages. Cotlet.dev connects your own Crexi account to any AI agent, so the AI searches listings, saves deals and tracks them for you.

What you can ask

Find retail properties for sale in Austin under $2M with a cap rate above 6%.

Save the 10 newest industrial listings in Phoenix to my "Q4 deals" list.

Compare these three listings: price per sq ft, cap rate, days on market.

Which of my saved properties dropped in price this week?

Export the contacts of brokers for my saved listings.

Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.

Claude Code

claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT

Settings → Apps → add connector URL https://cotlet.dev/mcp/v1, then sign in with Cotlet.dev. No API key needed.

Cursor

Copy .cursor/mcp.json from this repo into your project:

{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}

Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its Crexi tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

{"mcpServers":{"crexi":{"command":"uvx","args":["crexi-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}

Or with Docker:

docker build -t crexi-mcp .
docker run -i --rm -e COTLET_API_KEY crexi-mcp

Tools: crexi_guide, crexi_status, crexi_open, crexi_read, crexi_click, crexi_type, crexi_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

Command line

Python 3.10+, nothing else to install. From PyPI:

pip install crexi-mcp        # or run it once: uvx crexi-mcp connect
crexi-mcp connect

Or straight from this repo:

export COTLET_API_KEY="your-key"
python3 crexi_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 crexi_agent.py status    # is Crexi ready in your Cotlet.dev account
python3 crexi_agent.py guide     # Crexi screens and sign-in link
python3 crexi_agent.py read      # open Crexi, read the page, close the browser
python3 crexi_agent.py tools     # list Cotlet.dev tools
python3 crexi_agent.py serve     # start the stdio MCP server (same as no argument)

Questions from Crexi users

Does Crexi have an API?

Crexi has a Listing API only for qualifying MLSs, brokerages and data providers. Cotlet.dev works in your own Crexi account, so your AI agent can search and track deals without it.

How do I connect Crexi to ChatGPT?

Add Cotlet.dev as an app in ChatGPT (Settings → Apps, connector URL https://cotlet.dev/mcp/v1), sign in to Crexi once in your Cotlet.dev Cloud Browser, and ask ChatGPT in plain words. No code and no Crexi API key.

Is there a way to use Claude with Crexi?

Yes. In Claude Code run the one-line claude mcp add command above; in the Claude app add https://cotlet.dev/mcp/v1 as a custom connector. Claude then works in your own Crexi account.

Is there a Crexi MCP server?

Crexi has no official MCP server. Cotlet.dev is a hosted MCP server that works in Crexi for you, 24/7, with Claude, ChatGPT, Cursor, Codex, n8n, Make and Zapier.

Find it on

Also works with


More: https://cotlet.dev/integrations/crexi-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=crexi

Start free: https://cotlet.dev/signup?app=crexi&utm_source=github&utm_medium=readme&utm_campaign=crexi

Metadata

Release files for crexi-mcp 1.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Loss of provenance

These files do not have provenance metadata, despite files in a prior release including this data.

We recommend further investigation before installing these files. View details.

Source distribution (sdist)

Source distribution for crexi-mcp 1.1.0
File Size Uploaded Provenance Actions
crexi_mcp-1.1.0.tar.gz 8.4 kB Without provenance Details for crexi_mcp-1.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for crexi-mcp 1.1.0
File Interpreter ABI Platform Actions
crexi_mcp-1.1.0-py3-none-any.whl Python 3 none any Details for crexi_mcp-1.1.0-py3-none-any.whl

Total release size: 16.9 kB

Release files / crexi_mcp-1.1.0.tar.gz

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL crexi_mcp-1.1.0.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
aeb794f1fd0aba1e6a9af6eddbbc6c28dc3906232210c0d9314c62e5c8bea04f
BLAKE2b-256 checksum
How to use checksums
8e678e024f69ecc24f11204ae99ba729c271003632b82293b429339231a3a814
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.29 {"installer":{"name":"uv","version":"0.11.29","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / crexi_mcp-1.1.0-py3-none-any.whl

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL crexi_mcp-1.1.0-py3-none-any.whl
Size 8.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a5de8c45137e9657fc1b949d41bacea00380e3dff8cc6228ad8c302a03929916
BLAKE2b-256 checksum
How to use checksums
56135db4672a1c290331c74cbe0158bcaa8d340e8105e40e7da7b91cd8e3579c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.29 {"installer":{"name":"uv","version":"0.11.29","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for crexi-mcp 1.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Loss of provenance

A previous release of these files had provenance metadata, but this release does not.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Release comparison

  • Removed 1.0.0 2 files With provenance
  • Added 1.1.0 2 files Without provenance

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.1.0 This release

2 release files Loss of provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page