These steps follow Microsoft’s own setup for MCP servers.
In Copilot Studio, add a Model Context Protocol tool to your agent with this server URL:
https://app.tradiebridge.com/mcp
Choose OAuth 2.0 with dynamic discovery, then sign in to TradieBridge and approve the connection.
Before you start
- Nothing, if you’re new. The sign-in window creates your TradieBridge account from just your email, and you can connect Simpro there before you go back to Copilot. Paste a Simpro API key into TradieBridge and the first backup starts straight away.
- Access to Microsoft Copilot Studio.
Copilot also reads Xero, Verizon Connect, Deputy, Employment Hero, The Fleet Office, Dialpad, Moveware, ELMO and Emailed reports through the same link, if you connect them.
Add TradieBridge to a Copilot Studio agent
- In Copilot Studio, open the agent you want to use, or create one.
- Open Tools, then Add a tool → New tool → Model Context Protocol.
- Name it TradieBridge, describe it as “Answers from the business’s Simpro, Xero, Verizon Connect, Deputy, Employment Hero, The Fleet Office, Dialpad, Moveware, ELMO and Emailed reports backup”, and paste the link above as the server URL.
- For authentication, choose OAuth 2.0, then Dynamic discovery. Click Create.
- Create a connection. Copilot Studio sends you to TradieBridge. Sign in, then approve the connection.
- Add the tool to the agent, then test it in the agent’s test pane.
Tried it? Email [email protected] with what you saw, and we will update this page.
The Simpro MCP server
Copilot uses the same Simpro MCP server as the other assistants. That page covers what the server can read, how to disconnect it, and what to ask. Copilot can’t change anything in Simpro or any other system you connect. TradieBridge never writes to them. Copilot never sees tax file numbers, bank details or birth dates.