Connecting Model Match to Cursor

Connect Model Match to Cursor once and the agent can pull real originator and company data mid-task — no tab switching to look up a loan officer or check a company's volume.

In this article:

1. What the Model Match connector does
2. The Model Match connector (MCP server) URL
3. Adding the Model Match server in Cursor
4. Confirming the connection works
5. Frequently asked questions

What the Model Match connector does

The Model Match connector is a remote MCP server that gives Cursor's agent secure access to your Model Match workspace through the Model Context Protocol. Once it's connected, the agent can search and act on your data from inside a chat, without leaving the editor.

What it reaches:

• Loan Officers and Real Estate Agents: search by market, production, and tenure, and pull contact details straight into what you're building.
• Companies and lenders: roll up volume, look up branches, and trace where an originator sends business.
• Live market data: the same production and market activity you'd pull in Market Insights.
• Your own workspace: the agent can act on your Model Match records, not just query them.

Every tool call runs against your own Model Match sign-in, so the agent only ever reaches data you already have access to.

The Model Match connector (MCP server) URL

One address does the whole setup:

https://cursor.modelmatch.com/mcp

Adding the Model Match server in Cursor

Cursor reads MCP servers from a config file, so you're either using the settings UI to edit it or writing the entry by hand — both land in the same place.

1. Open Settings → Customize → Configure MCP servers, or edit the config file directly: ~/.cursor/mcp.json to make Model Match available in every project, or .cursor/mcp.json in a project root to scope it to just that one.
2. Add this entry and save:

{   "mcpServers": {     "modelmatch": {       "url": "https://cursor.modelmatch.com/mcp"     }   } }

1. Reopen the MCP settings, click modelmatch, and complete the browser sign-in.

💡 Cursor labels the server by the key you give it, not by any display name inside the entry. Keep the key modelmatch — that's what shows up in the tool picker, so a different key here makes the tools harder to spot later.

The server uses Streamable HTTP transport with OAuth, so there's no API key to paste. The first connection opens a browser window to sign in to Model Match and authorize access, and every tool call after that respects your existing workspace roles and permissions.

Confirming the connection works

Ask the agent something only Model Match can answer, right in a Cursor chat:

"Search Model Match for the top loan officers in Austin, TX this year."

You should get named originators with production figures back in the chat. If the agent doesn't reach for Model Match, open the MCP settings and check the server's status — an interrupted sign-in leaves it listed but unauthorized.

🧠 A project-level .cursor/mcp.json takes precedence over the global one for that project. If Model Match works in one project but not another, check whether a project-level config exists without the Model Match entry in it.

Frequently asked questions

Do I need a specific Cursor plan for this?

Model Match doesn't add a plan requirement beyond what your Cursor account already needs to configure MCP servers. You'll also need an active Model Match account, since the connection authenticates as you.

Is my data safe? What can the agent actually see?

The agent connects using your own Model Match sign-in, and every tool call respects your existing workspace roles and permissions. It reaches the same records you'd see in Model Match — nothing more.

Where do I paste the API key?

There isn't one to paste. The server uses OAuth over Streamable HTTP, so the url field in mcp.json is all the config needs — Cursor opens a browser window for the Model Match sign-in instead.

I added the entry to ~/.cursor/mcp.json but it's not showing up in one project — why?

A .cursor/mcp.json in that project's root overrides the global config for that project. Add the Model Match entry there too, or remove the project-level file if you meant to inherit the global one.

Why does the tool picker show "modelmatch" in lowercase instead of "Model Match"? Cursor labels the server by the JSON key you set, not a separate display name. Keeping the key as modelmatch is what the setup steps above use — you can rename the key, but the tool picker will always show whatever key you chose.

Can I connect Model Match to Cursor and Claude or ChatGPT at the same time?

Yes. One Model Match account can back connectors in several tools at once, each authenticating as you. See Connecting Model Match to Claude (Web, Desktop & Claude Code), Connecting Model Match to ChatGPT (for OpenAI Users), and Connecting Model Match to Perplexity.