Governed memory infrastructure

One secure gateway to Atlas memory.

Eventium MCP gives trusted AI applications a small, standards-based tool surface for durable project memory and behavioural rules—without exposing Atlas credentials, physical banks, or cross-user namespaces.

Connect an MCP client → Explore the seven tools
What it offers

Memory with a governed boundary.

This service is deliberately narrower than a general tool marketplace. Its production job is to make Atlas useful to Apex while keeping identity, authorization, session state, and persistence enforceable.

Durable recall

Retrieve project-specific evidence with source identifiers, routing score, and explicit out-of-domain state.

Meaningful recording

Persist verified facts, decisions, results, and checkpoints—not raw token streams or untrusted content.

Behavioural rules

Author and inspect project rules that Atlas binds to semantic request regions rather than keywords.

Canonical isolation

Derive private Atlas agent and bank names from immutable tenant, user, and project identities.

Session brokering

Maintain bounded, stable Atlas/D20k sessions and execute the documented user → agent → bank lifecycle inside the authenticated project boundary.

Operational visibility

Separate gateway liveness from authenticated Atlas readiness so failures remain diagnosable.

Architecture

Apex → MCP → Atlas.

Atlas is the memory engine; Eventium MCP is the secure protocol adapter. Browsers and sandboxes never call either service directly.

01 · EVENTIUM XUser experienceAuthenticates users and renders answers, evidence, and activity.
02 · EVENTIUM APIPublic BFFVerifies JWTs and authorizes the project request.
03 · APEXOrchestratorChooses an allowed Atlas operation. Canonical identity remains protected transport metadata.
04 · EVENTIUM MCPGoverned gatewayEnforces membership and role, then translates the operation.
05 · ATLAS D20kSystem of recordStores banks, retrieves evidence, matches rules, consolidates learning, and persists state.
Allowlisted surface

Exactly seven Atlas tools.

Every other tool is denied in the hosted production profile. Descriptions and JSON Schema metadata are published through MCP discovery so an LLM knows when—and when not—to invoke each operation.

01

Recall project memory

memory_recall

Semantically retrieves durable project memory, retrieval signals, and any matching behavioural rule.

Atlas/D20k · read
02

Store durable memory

memory_store

Persists one verbatim fact, decision, verified result, or checkpoint with optional provenance and indexing aids.

Atlas/D20k · write
03

Review recent learning

memory_recent

Returns a bounded tail of recent project memories and reports whether consolidation is due.

Atlas/D20k · recent
04

Consolidate related memories

memory_consolidate

Writes grouped summaries with source provenance while preserving the original project memories.

Atlas/D20k · summarize
05

Create a durability checkpoint

memory_persist

Forces project memory and behavioural rules to durable storage before a handoff or risky operation.

Atlas/D20k · persist
06

Author a behavioural rule

rule_add

Binds and persists a project rule from a natural-language exemplar and directive.

Atlas/D20k · rule write
07

List project rules

rules_list

Returns the bounded set of behavioural rules attached to the authenticated project.

Atlas/D20k · rule read
Authentication

Identity proof is not permission.

Every hosted Atlas call fails closed. A valid credential identifies the caller; active database membership and an allowed MCP role authorize the requested user namespace.

Supabase access token

Interactive clients may present a signed user JWT. The token UUID is bound to the target user and cannot select another namespace.

Registered MCP API key

Managed clients may use a hashed, revocable key linked to one Supabase user and checked against the same membership rules.

Apex service credential

The private service token authenticates Apex, but MCP still verifies the canonical target user’s active entitlement and role.

Both records are mandatoryatlas_api_access.active and mcp_user_roles.active with role developer or admin.
Identity stays outside tool argumentsTenant, user, project, and session scope are derived from authenticated request metadata and cannot be selected by the model.
No secrets in the browserAtlas credentials, physical bank names, internal session IDs, and the Apex service token remain server-side.
Client setup

Connect over Streamable HTTP.

Use an MCP client that supports the standard initialize → initialized → tools/list → tools/call lifecycle. Send credentials in the Authorization header; do not put secrets in tool arguments.

Eventium MCP client configuration
{
  "mcpServers": {
    "eventium-atlas": {
      "url": "https://mcp.eventium.ai/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer ${EVENTIUM_MCP_TOKEN}"
      }
    }
  }
}
Endpointhttps://mcp.eventium.ai/mcp
DiscoveryInitialize the session before calling tools/list. Only the seven Atlas tools should be returned.
Canonical argumentstenant_id, user_id, project_id, and session_id must come from verified application context.
Atlas response modelRecall returns raw evidence for the client model to synthesize. A memory write normally returns no retrieval context.
Operations & documentation

Small, useful, working links.

Authoring studios, public libraries, Swagger, and admin consoles are intentionally absent from this production navigation until they have a supported deployment and a clear Atlas-gateway purpose.

Gateway healthLiveness, version, deployed commit, and Atlas-only profile. Atlas readinessAuthenticated end-to-end Atlas/D20k lifecycle verification. OAuth metadataProtected-resource discovery for standards-aware clients.