Supported MCP Servers

The Aembit MCP Identity GatewayMCP Identity Gateway: A component that brokers MCP traffic between MCP clients and target MCP servers, validating authorization and presenting Aembit-managed credentials on each request.Learn more brokers AI agentAI Agent: A software workload that authenticates to systems, requests credentials, and accesses resources, either on behalf of a person or on its own. Aembit secures AI agents with the same identity-first model it uses for any workload. User-driven agents such as Claude Desktop also carry a blended identity that ties access to both the user and the agent.Learn more access to third-party MCP serversMCP Server: A server that implements the Model Context Protocol to provide tools, resources, or data to AI agents and MCP clients.Learn more(opens in new tab). It enforces Access PoliciesAccess Policy: Access Policies define, enforce, and audit access between Client and Server Workloads by cryptographically verifying workload identity and contextual factors rather than relying on static secrets.Learn more and injects per-user credentials, so agents never hold credentials directly.

Each of the following guides configures one MCP server to work through the Identity Gateway, using the MCP User-Based Access Token credential type.

MCP access vs. direct API access

These guides configure MCP tool access through the Identity Gateway. For direct REST API access to the same vendor (a traditional Server WorkloadServer Workload: Server Workloads represent target services, APIs, databases, or applications that receive and respond to access requests from Client Workloads.Learn more), see the Server Workload guides.

Supported servers

Configuration guides are available for the following servers:

Productivity

• Slack
• Notion
• Google Workspace: Drive, Calendar, and People

Data analytics

• BigQuery