Eventium.aiDocumentation

MODEL CONTEXT PROTOCOL

Governed Atlas tools for authorized clients.

Eventium MCP exposes a deliberately bounded Atlas memory surface over Streamable HTTP. It is a gateway, not a second memory authority.

Endpoint

https://mcp.eventium.ai/mcp

Lifecycle

  1. Send initialize with a supported protocol version.
  2. Retain the returned Mcp-Session-Id.
  3. Send notifications/initialized.
  4. Use tools/list to inspect the allowlisted surface.
  5. Invoke a tool with the same session and protocol headers.

Authentication and scope

Interactive clients use a verified user session; managed clients use an Eventium API key; internal Apex requests use a service credential plus verified target identity. In every case, MCP rechecks entitlement, role, project membership, and allowed operation.

Do not send identity as a model argument. Tenant, user, project, and session scope must come from trusted transport or application context.
MCP service
Capabilities and operational status.
API keys
Create a client credential.