Set up Copilot Studio

Configure the Amperity MCP server in Copilot Studio, after which the Amperity MCP server is available to any agent built in Copilot Studio, including agents published to the Microsoft 365 surface.

Requirements

Connecting Copilot Studio to the MCP server requires:

Copilot Studio

Use the Copilot Studio MCP onboarding wizard to configure server details and to configure OAuth.

  1. Open Copilot Studio.

  2. In Copilot Studio, open an agent.

  3. Go to the Tools page, select Add a tool, and then New tool.

  4. Select Model Context Protocol. The MCP onboarding wizard appears.

  5. Fill in the following fields:

    Field

    Value

    Server name

    “Amperity” or any name your team prefers

    Server description

    A short description of what the connector is for. The agent orchestrator uses this text to decide when to call Amperity at runtime.

    Server URL

    https://mcp.amperity.com

    Important

    Use the correct MCP server URL in the command.

  6. Under Authentication, select OAuth 2.0.

    Choose the Manual type and fill in the following fields.

    Field

    Value

    Client ID

    nwbd0MGCyh1VysmYQM05UoDXIuVPdGEs

    Client secret

    Any non-empty placeholder, for example “unused”. The Amperity MCP server is a PKCE-based public OAuth client and ignores this value, but Copilot Studio requires the field to be non-empty.

    Authorization URL

    https://mcp.amperity.com/authorize

    Token URL template

    https://mcp.amperity.com/oauth/token

    Refresh URL

    https://mcp.amperity.com/oauth/token

    Important

    Use the correct MCP server URL in the command, and then append /authorize and /oauth/token to that URL for the Authorization URL, Token URL template, and Refresh URL values.

  7. Select Create. Copilot Studio displays a callback URL. The Amperity OAuth proxy registers the callback URL dynamically.

  8. Select Next to continue. On the Add tool dialog, choose Create a new connection and sign in with your Amperity credentials.

  9. Select Add to agent.

Tool surface limits

Copilot Studio limits the number of tools an agent can register. The full Amperity MCP surface exposes more than 200 tools, so most agents will need to scope down the number of tools. There are two options:

  1. Use a persona-scoped MCP server. Amperity publishes split MCP servers that expose a smaller, role-scoped tool surface for clients with tool-count limits. Contact your Amperity representative for access.

  2. Restrict your agent to a subset of tools. On your agent’s Tools tab, select the Amperity MCP server to open its settings page. Under the Tools section, turn off the Allow all toggle, and then use the individual toggles to enable only the tools your agent needs.

    Important

    Tools added to the Amperity MCP server are turned off by default when Allow all is disabled.

Start interacting with Copilot

Open a chat in any Microsoft 365 application in which an agent with access to the Amperity MCP server is configured. Ask the agent about your Amperity tenant:

"Tell me about my Amperity tenant."

The agent calls the tenant_info tool and returns details about your current Amperity tenant.

Tip

If the agent returns an authorization error, sign out, and then reauthorize the connector.