Skip to main content
Connect CivicMarketplace to Microsoft 365 Copilot so your team can ask about contracts and suppliers from inside Copilot.
Adding an MCP connector to Microsoft 365 Copilot is done through Copilot Studio and typically requires a Microsoft 365 Copilot license plus permission to build or publish agents in your tenant. Check with your Microsoft 365 administrator if you don’t have access.
The endpoint you’ll use:

​
Add the connector in Copilot Studio

1

Open Copilot Studio

Go to copilotstudio.microsoft.com and open (or create) the agent you want to extend.
2

Add a tool / MCP server

In the agent, go to Tools → Add a tool → Model Context Protocol (or New tool → MCP), and enter the server URL https://mcp.civicmarketplace.com/mcp.
3

Configure OAuth

Choose OAuth authentication. Copilot Studio uses CivicMarketplace as the identity provider — users sign in with their own CivicMarketplace account and approve the requested permissions the first time they use the connector.
4

Publish and test

Save and publish the agent. In Copilot, ask the agent something like “Search CivicMarketplace for HVAC contracts.” The first request prompts each user to sign in.
Each user authenticates as themselves, so results are always scoped to what that person’s CivicMarketplace account can access — no shared credentials.

​
Troubleshooting

MCP support and the exact menu names roll out gradually across tenants and may require specific licensing. Make sure your tenant has Copilot Studio enabled and you have rights to add tools to agents.
Confirm the tool’s authentication is set to OAuth (not “no authentication”). Re-publish the agent after changing authentication settings.
The connector only returns data a user’s CivicMarketplace account can access. If a user expects more, their CivicMarketplace access may need to be updated — contact your account manager.

​
Next steps

Example prompts

See what you can ask once you’re connected.

Tools and permissions

Review the MCP tools and required permissions.