🧪

This feature is still under active development.

Toqua MCP Server

The Toqua MCP server lets AI assistants and agents access Toqua's API on your behalf, using natural language. Below guides explains how to connect it to your tools: ChatGPT, Copilot, Claude, ...

Server details

Authentication is handled through OAuth. When you first connect, you'll be redirected to sign in and authorize access.

Connecting with Microsoft Copilot (Copilot Studio)

Connecting to an external MCP server is done in Copilot Studio, then the server is added to an agent as a tool. This usually requires the appropriate Power Platform and Copilot Studio permissions, so your IT or platform administrator is generally the right person to do it.

1. Add the MCP server

1. In Copilot Studio, select the environment you want to work in.
2. Open your agent (or create a new one) and go to the Tools page.
3. Select Add a tool, then New tool, then Model Context Protocol.
4. In the onboarding wizard, fill in:
   • Server name — e.g. Toqua
   • Server description — e.g. Monitor your fleet's performance
   • Server URL — https://api.toqua.ai/mcp
   • Authentication — OAuth 2.0
     • Type — Dynamic Discovery
5. Complete the wizard. Copilot Studio creates a custom connector behind the scenes that routes requests to the server over Streamable HTTP.

Note: The MCP onboarding wizard, which handles OAuth discovery automatically, is still rolling out and may not be enabled for every tenant or region. If selecting Model Context Protocol only opens a documentation page instead of the wizard, your tenant likely hasn't received the feature yet. In that case, open a Microsoft support ticket to check your rollout status — the manual "custom connector" path does not support automatic OAuth discovery.

2. Authorize and connect

1. The first time the connection is used, you'll be prompted to authenticate. Select Create connection and sign in.
2. You'll be redirected to authorize Toqua access via OAuth. Approve the request to complete the connection.

3. Add the server to your agent

1. On the Tools page, select Add a tool, then Model Context Protocol.
2. Select the Toqua connector from the list.
3. Select Add and configure. The Toqua tools become available to your agent.

You can now ask the agent questions about your fleet, and it will use the Toqua tools to answer.

Connecting with ChatGPT

In ChatGPT, the Toqua MCP server is added as a custom app. A short walkthrough video is available here: https://www.loom.com/share/d557604099044f33875d9eb242b0e49d

1. First, make sure Developer Mode is enabled. Go to Settings → Apps → Advanced Settings and enable Developer Mode
2. Go to Settings → Apps and choose Create App next to Advanced Settings.
3. Enter the server URL: https://api.toqua.ai/mcp
4. Save and connect. You'll be redirected to sign in and authorize access via OAuth.
5. Once connected, enable the Toqua connector in a chat to let ChatGPT use its tools.

Connecting with Claude

In Claude, the Toqua MCP server is added as a custom connector. It works across Claude, Claude Desktop, and the mobile apps, on Pro, Max, Team, and Enterprise plans.

On Team and Enterprise plans, only an Owner can add the connector via Organization Settings → Connectors. Once added, each member connects and authorizes individually. On Pro and Max, you add it directly in your own settings.

1. Go to Settings → Connectors (or Customize → Connectors).
2. Click the + next to Connectors, then Add custom connector.
3. Enter a name (e.g. Toqua) and the server URL: https://api.toqua.ai/mcp. You can leave the advanced OAuth settings blank — Toqua handles registration automatically.
4. Click Add, then Connect, and sign in to authorize access via OAuth.

Troubleshooting

• Authorization fails or loops — make sure pop-ups and redirects to Toqua's sign-in page aren't blocked by your browser or network policy.
• Connector blocked in Copilot Studio — check that the environment isn't restricted by a DLP policy; use a Developer or Sandbox environment.
• Tools don't appear — confirm the connection authorized successfully and that the server was added to the specific agent.

If you run into issues that aren't covered here, contact [email protected].