Skip to content
Submit a ticket
  • There are no suggestions because the search field is empty.

Connecting Model Match to Microsoft Copilot Studio

Add Model Match as an MCP tool in Microsoft Copilot Studio so any agent you build can search Loan Officers, Real Estate Agents, Companies, and lenders.

Connect Model Match to Microsoft Copilot Studio once, and every agent you build there — for recruiting, for market research, for anything — can reach real originator and company data as one of its tools.

In this article:

  1. What the Model Match connector does
  2. The Model Match connector (MCP server) URL
  3. Adding the Model Match tool to an agent
  4. How Power Platform data policies affect this connection
  5. Confirming the connection works
  6. Frequently asked questions

What the Model Match connector does

The Model Match connector is a remote MCP server that gives a Microsoft Copilot Studio agent secure access to your Model Match workspace through the Model Context Protocol. Once it's added as a tool, the agent can search and act on your data at runtime, not just read it.

What it reaches:

  • Loan Officers and Real Estate Agents: search by market, production, and tenure, and pull contact details for the agent to act on.
  • 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://copilot.modelmatch.com/mcp

Adding the Model Match tool to an agent

Let's add Model Match to a specific agent — Copilot Studio attaches MCP tools per agent, so you'll repeat this for each agent that needs it.

  1. Open the Tools page for your agent, then select Add a tool → New tool → Model Context Protocol.
  2. Fill in Server name (Model Match), Server description, and the server URL above.
  3. Choose OAuth 2.0 as the authentication type, then Dynamic discovery. Model Match supports OAuth 2.0 dynamic client registration with discovery, so Copilot Studio finds the endpoints and registers itself — there's no client ID, secret, or callback URL to copy.
  4. Select Create, then Next.
  5. On Add tool, choose Create a new connection, sign in to Model Match, then select Add to agent.

💡 Write the server description carefully — the agent orchestrator reads it at runtime to decide whether Model Match is relevant to a given request at all. A vague description means the agent may skip Model Match even when it has the answer.

Model Match uses the Streamable transport, which is what Copilot Studio supports, so there's nothing to configure there. Once it's added, every tool call the agent makes respects your existing workspace roles and permissions.

How Power Platform data policies affect this connection

🧠 Copilot Studio reaches MCP servers through Power Platform connectors, so the same data policies that govern any other Power Platform connector govern this one too. If a policy blocks the connector, the agent loses the Model Match tools along with it — the fix lives in your Power Platform admin settings, not in the agent's Tools page.

The same connection works from Power Automate and Power Apps, so a Model Match connection you've approved for one surface is available to the others under the same policy.

Confirming the connection works

Open the agent and ask it something only Model Match can answer:

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

You should get named originators with production figures back from the agent. If the agent doesn't reach for Model Match at all, revisit the server description from the setup step — that's usually the reason the orchestrator skips a tool it has access to.

If the agent reports it can't reach the tool rather than ignoring it, check the connection's status on the Tools page — an interrupted OAuth sign-in leaves the tool listed but unauthorized.

Frequently asked questions

Do I need a specific Copilot Studio license for this?

Model Match doesn't add a licensing requirement beyond what your organization already needs to add MCP tools in Copilot Studio. 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 enter a client ID or secret?

Nowhere — choose Dynamic discovery under OAuth 2.0 and leave it there. Model Match supports OAuth 2.0 dynamic client registration with discovery, so Copilot Studio finds the endpoints and registers itself without a client ID, secret, or callback URL.

My agent has the Model Match tool but never uses it — why?

The agent orchestrator decides whether to call a tool based on its server description, not just its presence in the Tools list. Go back to Add a tool and sharpen the description so it clearly states what Model Match can answer.

A Power Platform data policy is blocking Model Match — who fixes that?

Your Power Platform admin, not you, from the data policy settings that govern Power Platform connectors generally. Copilot Studio reaches Model Match through that same connector layer, so a policy that blocks it there removes the tool from every agent using it.

Can I use the same Model Match connection in Power Automate or Power Apps?

Yes. The connection works across Power Automate and Power Apps under the same Power Platform data policy, so approving it once covers all three surfaces.