Amplify's AI Assistant can be added to Claude as a custom connector using the Model Context Protocol (MCP). Once connected, Claude can answer questions about Amplify data — initiatives, benefits, costs, RAID items and tasks — using the Amplify permissions of the person who connects.
This article covers Claude Team and Enterprise plans. An Owner adds the connector once for the organization. Each member then connects it to their own Amplify account.
Note MCP access is in Beta and needs to be enabled for your organization. Speak to your Customer Success Manager to have it enabled. The AI Assistant (MCP) OAuth section does not appear on the Authentication page until MCP access is enabled.
Prerequisites
- Administrator privileges in Amplify.
- A Claude Team or Enterprise plan.
- The Owner or Primary Owner role in Claude. On Enterprise plans, a member with a custom role that includes managing the organization's libraries can also add connectors.
- An Amplify account for each member who will connect.
Collecting the MCP connection details in Amplify
To prepare Amplify for Claude:
- Click your profile icon in the top right corner.
- Click Administration.
- Go to Authentication in the side menu.
- Scroll to the AI Assistant (MCP) OAuth section.
- Copy the MCP Server URL. You enter this in Claude in the next section.
- Copy the Client ID and Client Secret. You enter these in Claude in the next section.
- Add both of these URLs to the Redirect Whitelist:
https://claude.ai/api/mcp/auth_callback https://claude.com/api/mcp/auth_callback - Click Save.
Claude returns users to the first URL after sign-in. Anthropic has said it may move to the second URL in future, so whitelisting both keeps the connector working if that happens.
Treat the client secret like a password. Paste it straight into Claude. Do not email it, put it in a ticket, or store it in a shared document.
Adding the connector in Claude
An Owner completes these steps once for the whole organization. To add the connector:
- In Claude, go to Organization settings > Connectors.
- Select Add, then Custom. If Claude asks for a connector type, choose Web.
- Enter a name your members will recognize, for example Amplify.
- Enter the Amplify MCP Server URL as the remote MCP server URL.
- Where the dialog asks for Authentication, select Sign in now.
- Where the dialog asks for OAuth client, select Use your own OAuth client, then enter the Client ID and Client Secret from Amplify. Where the dialog instead shows Advanced settings, open it and enter the Client ID and Client Secret there.
- Click Add.
The connector appears for every member under Customize > Connectors, with the Custom label.
The Client ID and Client Secret cannot be changed in Claude after the connector is added. Where either value changes in Amplify, remove the connector in Claude and add it again with the new values. Every member then needs to reconnect.
Connecting Amplify in Claude
Share these steps with members once the connector has been added. Each member does this once. To connect:
- In Claude, go to Customize > Connectors.
- Find the Amplify connector, labeled Custom.
- Click Connect. The Amplify login page opens.
- Sign in to Amplify.
- Click Allow to grant read access.
The connector shows as connected and is available in Claude on the web, Claude Desktop and the Claude mobile app.
To use Amplify in a chat, click the + button, select Connectors, and turn the Amplify connector on.
Note Access is read-only. Claude only sees the Amplify data the member's own Amplify permissions allow. Connecting in Claude does not grant access to anything the member cannot already see in Amplify.
Troubleshooting
- The connector does not appear under Customize > Connectors. Confirm an Owner added it under Organization settings > Connectors, and that the member is signed in to that organization in Claude.
- Sign-in works but the connection fails at the end. Most often this is the redirect URL. Confirm both Claude URLs are in the Redirect Whitelist in the AI Assistant (MCP) OAuth section.
- Client or token errors. Confirm the Client ID and Client Secret entered in Claude match the current values in Amplify. Where they don't match, remove the connector in Claude and add it again with the current values.
- The member connects but Claude returns no Amplify data. Check the member's permissions in Amplify. Claude can only return what that member can already see.
- Claude does not use Amplify in a chat. Confirm the connector is turned on for that chat under + > Connectors.
If the problem persists, contact Amplify Support with the connector name, the Amplify instance URL, and the exact error message shown. Do not include the client secret.
For Microsoft tools, see Configuring MCP Access for Microsoft 365 Copilot and Configuring MCP Access for Microsoft Copilot Studio Agents.