Skip to content

The Aembit Model Context Protocol (MCP) Server is a secure, read-only API layer that enables AI agents and users to query Aembit event logs using structured commands. Built on the Model Context Protocol specification, this service enables agentic observability and auditability for organizations using Aembit.

You can query audit logs, authorization events, and Workload: Any non-human entity (application, service, automation, etc.) that needs to access resources.Learn more events through integrations with tools like MCP Inspector, Claude Code, GitHub Copilot, and Visual Studio. See Audit and report on Workload activity to learn more about Aembit event logs.

The MCP Server enforces multiple layers of access control:

  • Authentication - API Token authentication via the Authorization: Bearer header. Generate tokens from the Aembit Admin UI Profile page.
  • Authorization - Resource Set: Resource Sets are organizational containers that group Access Policy components together, enabling you to manage configurations across different environments, regions, or use cases.Learn more-based scoping restricts queries to resources in the assigned set, enforcing least-privilege access.
  • Read-only access - The MCP Server supports only read operations. You can’t create, update, or delete data.
  • Audit trail - Aembit logs all MCP Server queries, including the identity of the requesting agent.

The MCP Server provides access to operational event metadata such as timestamps, event types, and workload identifiers. It doesn’t expose secrets, credentials, or sensitive configuration data.

For more detail on how these mechanisms work, see About the MCP Server.

The following pages provide information about the Aembit MCP Server:

Evaluating the MCP Server for your organization? Start with About the MCP Server for security model and access control details. Ready to integrate? Jump to Connect to the MCP Server for authentication and client setup guides.