Back to MCP Servers
🧩

Cratis Chronicle MCP Server

API key required

Inspect Cratis Chronicle event stores read-only by default; opt-in, authorized job control.

To add Cratis Chronicle to Claude, run the install command below. Restart Claude Code after adding it and its tools show up in your next conversation. It needs 7 environment variables, listed below.

DevTools

Install

docker run -i --rm docker.io/cratis/chronicle-mcp:2.0.0

Environment variables

Cratis__Chronicle__Mcp__ProfileSet in your MCP config
Cratis__Chronicle__Mcp__ConnectionStringSet in your MCP config
Cratis__Chronicle__Mcp__ClientIdSet in your MCP config
Cratis__Chronicle__Mcp__ClientSecretSet in your MCP config
Cratis__Chronicle__Mcp__ApiKeySet in your MCP config
Cratis__Chronicle__Mcp__EventStoreSet in your MCP config
Cratis__Chronicle__Mcp__NamespaceSet in your MCP config

What this does

Cratis Chronicle exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

Cratis__Chronicle__Mcp__Profile
Cratis__Chronicle__Mcp__ConnectionString
Cratis__Chronicle__Mcp__ClientId
Cratis__Chronicle__Mcp__ClientSecret
Cratis__Chronicle__Mcp__ApiKey
Cratis__Chronicle__Mcp__EventStore
Cratis__Chronicle__Mcp__Namespace

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install Cratis Chronicle?

The install section on this page carries the maker's install command for Cratis Chronicle, as submitted. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Cratis Chronicle?

This page carries setup and config for Claude Code. Any other MCP client that accepts a standard server config can connect to Cratis Chronicle as well.

Does Cratis Chronicle need an API key?

Yes. Before it can run, set these environment variables: Cratis__Chronicle__Mcp__Profile, Cratis__Chronicle__Mcp__ConnectionString, Cratis__Chronicle__Mcp__ClientId, Cratis__Chronicle__Mcp__ClientSecret, Cratis__Chronicle__Mcp__ApiKey, Cratis__Chronicle__Mcp__EventStore, Cratis__Chronicle__Mcp__Namespace. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-cratis-chronicle-mcp)](https://clauderules.net/mcp/io-github-cratis-chronicle-mcp)
HTML
<a href="https://clauderules.net/mcp/io-github-cratis-chronicle-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-cratis-chronicle-mcp" alt="Listed on clauderules.net" /></a>