Build and connect
Give AI teammates approved tools
Register MCP servers in Alloy, test the connection, and choose which AI teammates are allowed to use each server.
What MCP servers are for
MCP servers let Alloy connect AI teammates to external tools and systems through a standard tool interface. Instead of giving every AI teammate every integration, teams can register servers once and assign them where they are needed.
Use MCP servers when an AI teammate needs controlled access to a business system, custom tool, database, or service that your team exposes through MCP.
Register servers at the organization level
The MCP Servers page lets your team add, edit, test, and delete organization MCP servers. Each server can have a name, URL, and optional headers.
Alloy currently accepts `http://` and `https://` URLs when creating an MCP server. Headers can use organization variables and secrets so teams can keep credentials out of visible copy.
Assign tools to the right teammate
After a server is registered, AI teammate detail pages include an MCPs tab. From there, staff can enable or disable each organization MCP server for that teammate.
This keeps tool access scoped. A support AI teammate can get support tools, while an operations AI teammate can get operations tools.
Test before use
Alloy includes a connection test for stored MCP servers. The test sends an initialization request and shows whether the server responded successfully, including status and response body when available.
Testing helps teams catch URL, credential, and server compatibility problems before an AI teammate depends on the tool.
Frequently asked questions
Are MCP servers shared across the whole workspace?+
They are registered at the organization level, but each AI teammate must be assigned the servers it uses.
Can MCP server credentials use secrets?+
Yes. Runtime URL and header values can use organization variables, including secrets.
Can AI teammates delete MCP servers?+
No. MCP delete remains human-only in the current behavior.