Set up Microsoft Copilot and Foundry¶

Connect Microsoft’s agent products to the Amperity MCP server and sign in with your Amperity credentials. This page covers four clients:

VS Code – GitHub Copilot in agent mode.
GitHub Copilot CLI – the terminal agent.
Copilot Studio – the agent builder for Microsoft 365.
Microsoft Foundry – Foundry Agent Service.

Important

These are separate Microsoft products and they receive different tool surfaces. VS Code and GitHub Copilot CLI receive the full tool surface. Copilot Studio and Microsoft Foundry receive a curated subset of tools–see Tool surface limits.

VS Code¶

Configure the Amperity MCP server in VS Code, after which the Amperity tools are available to GitHub Copilot in agent mode.

Requirements¶

Connecting VS Code to the MCP server requires:

An active Amperity account with access to at least one tenant.
GitHub Copilot, signed in with an account that has an active Copilot subscription. Agent mode is required.

Add the Amperity MCP server¶

Add the Amperity server to your user-level MCP configuration file, which makes Amperity available in every VS Code workspace.

Open the Command Palette (Ctrl+Shift+P on Windows and Linux, Cmd+Shift+P on macOS), and then run MCP: Open User Configuration.

Add the amperity server:

{
  "servers": {
    "amperity": {
      "type": "http",
      "url": "https://mcp.amperity.com"
    }
  }
}

Save the file. VS Code detects the new server automatically.
Open the Command Palette, run MCP: List Servers, select amperity, and then select Start.
A browser window opens. Sign in with your Amperity credentials.

Start interacting with Copilot in VS Code¶

Open Copilot Chat, set the mode to Agent, and then ask about your Amperity tenant:

"Tell me about my Amperity tenant."

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

GitHub Copilot CLI¶

Configure the Amperity MCP server in GitHub Copilot CLI, after which the Amperity tools are available to the agent in your terminal.

Requirements¶

Connecting GitHub Copilot CLI to the MCP server requires:

An active Amperity account with access to at least one tenant.
GitHub Copilot CLI installed, and a GitHub account with an active Copilot subscription.

Install the CLI with npm:

npm install -g @github/copilot

Add the Amperity MCP server¶

Add the server:
```
copilot mcp add --transport http amperity https://mcp.amperity.com
```
This writes the server to your user configuration at ~/.copilot/mcp-config.json. Confirm it with copilot mcp list.
Start an interactive session:
```
copilot
```
Authorize the server:
```
/mcp auth amperity
```
A browser window opens. Sign in with your Amperity credentials. The browser confirms Authorization Successful; close it and return to the terminal.

Start interacting with Copilot CLI¶

In an interactive session, ask about your Amperity tenant:

"Tell me about my Amperity tenant."

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

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:

An active Amperity account with access to at least one tenant.
Access to Copilot Studio with permission to add custom connectors.

Add the Amperity MCP server¶

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

Open Copilot Studio.
In Copilot Studio, open an agent.
Go to the Tools page, select Add a tool, and then New tool.
Select Model Context Protocol. The MCP onboarding wizard appears.

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

Under Authentication, select OAuth 2.0, and then choose the Dynamic discovery type.
Select Create, and then Next to continue. On the Add tool dialog, choose Create a new connection and sign in with your Amperity credentials.
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, which exceeds this limit.

To stay within the limit, the Amperity MCP server automatically detects Copilot Studio connections and serves a curated subset of tools sized to fit within Copilot Studio’s connector tool limit. No manual configuration is required–connect Copilot Studio by following the steps above, and your agent receives the curated tool set automatically.

Note

This curated subset is specific to Copilot Studio. It is the server’s response to Copilot Studio’s connector tool limit, and it does not apply to other clients. In particular, VS Code receives the full tool surface, so a tool available to Copilot in VS Code may not be available to a Copilot Studio agent.

To narrow the surface further, restrict your agent to a smaller 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.

Microsoft Foundry¶

Connect a Microsoft Foundry agent to the Amperity MCP server. Amperity is listed in the Foundry Tool Catalog.

Requirements¶

Connecting Foundry to the MCP server requires:

An active Amperity account with access to at least one tenant.
A Foundry project with a model deployment.
The Foundry User role on the project to build the agent.

Connect the Amperity tool¶

Create a project connection that holds the Amperity endpoint and its OAuth settings.

In the Foundry portal, open your agent and go to Tools.
Select Add, open the Catalog tab, and then search for Amperity.
Select the Amperity entry. The Connect the Amperity tool dialog opens with the server endpoint already filled in as https://mcp.amperity.com/mcp.
Leave Authentication set to OAuth Identity Passthrough.

Under OAuth Provider, select Custom, and then fill in the following fields:

Field	Value
Client ID	`nwbd0MGCyh1VysmYQM05UoDXIuVPdGEs`
Client secret	Enter `placeholder`. Foundry requires this field, but Amperity is a public OAuth client and issues no secret, so the value is ignored.
Auth URL	https://mcp.amperity.com/authorize
Token URL	https://mcp.amperity.com/oauth/token
Refresh URL	https://mcp.amperity.com/oauth/token
Scopes	`openid offline_access`

Select Connect, and then save the agent.

Tool surface limits¶

Foundry agents receive the same curated subset of tools as Copilot Studio. See Tool surface limits.

Start interacting with your agent¶

Open the agent in the playground and ask 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.

Choose topic collections

Set up Microsoft Copilot and Foundry¶

VS Code¶

Requirements¶

Add the Amperity MCP server¶

Start interacting with Copilot in VS Code¶

GitHub Copilot CLI¶

Requirements¶

Add the Amperity MCP server¶

Start interacting with Copilot CLI¶

Copilot Studio¶

Requirements¶

Add the Amperity MCP server¶

Tool surface limits¶

Start interacting with Copilot¶

Microsoft Foundry¶

Requirements¶

Connect the Amperity tool¶

Tool surface limits¶

Start interacting with your agent¶