Skip to main content
Connect Microsoft Copilot Studio to Aries so you can use the Aries API (portfolio, market data, orders) from your Copilot agents. You add the Aries MCP server as a tool, configure Manual OAuth 2.0 with the Aries authorization and token URLs, enter your Client ID, then create a connection and complete the Aries OAuth screen in your browser (same flow as other platforms).

What you need


Step 1: Add the MCP tool and get your Redirect URL

In Copilot Studio you will add the Aries MCP server as a tool and configure OAuth. The Redirect URL is generated by Copilot Studio (e.g. when you save). You need this URL for Step 2 (Client Center).
  1. Go to Microsoft Copilot Studio and sign in with your Microsoft account.
  2. Create a new agent or open an existing agent.
  3. In the agent, go to ToolsAdd a toolNew tool.
  4. Select Model Context Protocol. The MCP onboarding wizard appears.
  5. Enter the tool details:
    • Name — e.g. Aries or Aries MCP (or any name you prefer).
    • Description — Optional; e.g. “Aries trading API”.
    • Server URL — Enter this exact URL (fixed for all users):
      https://mcp.aries.com/mcp
      
  6. Under Authentication, select OAuth 2.0.
  7. For discovery type, select Manual (not Dynamic).
  8. In the Manual OAuth form, fill in the Aries endpoints (Client ID and Client secret will be filled in Step 3):
    • Authorization URL — Enter exactly:
      https://app.aries.com/oauth2/authorize
      
    • Token URL template — Enter exactly:
      https://api.aries.com/v1/oauth2/token
      
    • Refresh URL — Enter exactly (same as token URL):
      https://api.aries.com/v1/oauth2/token
      
    • Scopes — Optional; e.g. the scopes you want (see OAuth2 Guide — Scopes). You will configure the same scopes in Client Center.
  9. Find the Redirect URL field. Copilot Studio may show a read-only value such as “The redirect URL will be generated when you save…” with a Copy option. Save or Create the tool if needed so the Redirect URL is generated, then copy that Redirect URL — you will use it in Step 2.
Enter the Server URL exactly: https://mcp.aries.com/mcp (no trailing slash). The Authorization URL, Token URL, and Refresh URL must match the values above. You will add the Redirect URL from Copilot Studio into Client Center in Step 2.

Step 2: Create an OAuth client in Client Center (get your Client ID)

Create an OAuth client in Client Center using the exact Redirect URL you copied from Copilot Studio in Step 1. Aries only requires a Client ID (no client secret for this MCP flow).
  1. Open Client Center and go to the API section.
  2. Click Generate Key.
  3. Fill in:
    • Client name — e.g. “Copilot Studio MCP”.
    • Redirect URI — Paste the exact Redirect URL you copied from Copilot Studio (Step 1). It must match exactly or authorization will fail.
    • Scopes — Choose what you want the agent to do (e.g. read account, place orders, market data). Use the same scopes as in Copilot Studio if you entered any.
  4. Save and copy your Client ID. You will enter this in Copilot Studio in Step 3. Client ID is required — the connection will not work without it.
The Redirect URI in Client Center must match the Redirect URL from Copilot Studio exactly (no trailing slash, same scheme and path). If they differ, you will get a redirect_uri_mismatch error.

Step 3: Enter Client ID in Copilot Studio and create the connection

Back in Copilot Studio, enter your Client ID and finish the tool setup. Aries only requires Client ID; leave Client secret blank if the form allows it.
  1. In the MCP tool OAuth configuration (Manual), enter:
    • Client ID — Paste your Client ID from Step 2.
    • Client secretLeave blank if the UI allows. Aries MCP does not use a client secret; if the form requires a value, try leaving it blank first. Some OAuth UIs accept Client ID only.
  2. Save or Create the tool, then click Next.
  3. You will see a Connection that is not connected. Click that connection (or Create new connection).
  4. Click Create to create the connection. This starts the Aries OAuth flow.
Client secret: Aries only requires your Client ID for this MCP connection. If Copilot Studio’s form marks Client secret as required and does not accept a blank value, try entering a single space or contact your admin; the Aries authorization server does not use client secret for this flow.

Step 4: Complete the Aries OAuth screen and grant permission

When you create or open the connection, your browser opens the Aries OAuth screen so you can sign in and grant access.
  1. Your browser opens the Aries OAuth screen (sign-in and consent page).
  2. Sign in with your Aries email and password.
  3. Review the permissions and click Allow or Approve to grant access.
First-time permission grant: This screen appears only the first time you connect. If you close it without clicking Allow, it may not appear again. Complete sign-in and click Allow or Approve before closing the tab.
  1. After you approve, Aries redirects back and the token exchange completes. You should see a success message or return to Copilot Studio with the connection showing as connected.

Step 5: You’re connected

Your Copilot Studio agent is now linked to your Aries account. You can use the Aries MCP tool in your agent within the scopes you granted (e.g. portfolio, market data, orders).

Troubleshooting

IssueWhat to do
”redirect_uri_mismatch”The Redirect URI in Client Center must match the Redirect URL from Copilot Studio exactly. Copy the URL from Copilot Studio again (after saving the tool) and set it in Client Center when generating the key. No trailing slash.
”invalid_client”Confirm your Client ID is correct and the client is active in Client Center. Ensure you pasted the Client ID in the Copilot Studio OAuth form.
Client secret requiredAries does not use a client secret for this flow. Leave Client secret blank if allowed; if the form rejects blank, try a placeholder and ensure Client ID is correct.
Permission screen didn’t appear or I missed itThe grant screen only appears the first time. Complete sign-in and click Allow before closing the browser tab. If you missed it, remove the connection and create it again, then complete the OAuth screen.
More help: OAuth2 Guide — Troubleshooting.

Next steps