Docs — Setup & API
Setup Guide
Get AxiomSeal running in about 10 minutes.
1. Install your AI client
AxiomSeal is a standard remote MCP server, so it works with any MCP-compatible AI client. Pick the one you use — the connection config in section 2 is shared across all of them.
Option A: Claude Code CLI (recommended)
Requires Node.js 18+. After install, run 'claude' in your project directory.
npm install -g @anthropic-ai/claude-code
Documentation: docs.anthropic.com/claude-code
Option B: VS Code Extension
- 1. Open VS Code
- 2. Go to Extensions (Ctrl+Shift+X)
- 3. Search for “Claude Code” by Anthropic
- 4. Click Install
Or install directly: VS Code Marketplace
Option C: Claude Desktop App
Download from claude.ai/download (macOS, Windows, Linux). After install: Settings → Developer → MCP Servers.
Option D: Cursor / VS Code
Both support MCP. In Cursor: Settings → MCP → add a server with the config in section 2 (or use the one-click Add to Cursor button on the homepage). In VS Code: add the same server to .vscode/mcp.json in your workspace.
Option E: ChatGPT (Plus / Pro / Team / Enterprise)
In ChatGPT open Settings → Connectors → Add custom connector, choose MCP server, and enter https://mcp.axiomseal.com/mcp/. Authorize with one click (OAuth). Requires a plan where custom connectors / developer mode are enabled.
Option F: Gemini CLI
Add AxiomSeal to ~/.gemini/settings.json under mcpServers using the config in section 2 (use the httpUrl field for the URL). Then run gemini — the memory tools are available.
Option G: Other MCP clients & local models
Any MCP-capable client works — for example Cline, Continue, or a local model via LM Studio or an MCP bridge. Point the client at https://mcp.axiomseal.com/mcp/ with the Authorization header from section 2.
Folder Restriction (Sandbox)
For security, limit which folders your AI assistant can access:
- CLI: Start
claudeinside your project folder. It can only access the current directory and subdirectories. - VS Code: Open only the folder you want to work in. The extension operates within your workspace.
- Desktop: Settings → Developer → Allowed Directories. Add only the folders you need.
Tip: Create a dedicated project folder for each project. Start Claude only there.
Important Notice
- AI assistants can read and modify files in your permitted directories
- You are responsible for reviewing all AI-generated code before deploying it
- Do not store passwords, API keys, or secrets as memories — known key formats are redacted, passwords in free text are not reliably caught
- We do not guarantee the correctness of AI-generated outputs
- AxiomSeal assumes no liability for damages arising from use
- You use this service at your own risk
2. Connect AxiomSeal
Step 1: Get your API Key
Create an account and copy your API key from the dashboard. Your key starts with eon_.
Step 2: Connect
Claude Code, Claude Desktop and ChatGPT connectors authorize through your browser and need no API key at all. Clients that cannot do OAuth (Gemini CLI, local-model bridges) use the manual config in step 3 below.
1. One command
No API key needed. Your browser opens, you log in, and you are connected. Nothing is written into your project folder.
Works in Claude Code. Restart your client afterwards.
claude mcp add --transport http axiomseal https://mcp.axiomseal.com/mcp/
Working across several projects? Add --scope user and it is set up once for your whole account:
claude mcp add --scope user --transport http axiomseal https://mcp.axiomseal.com/mcp/
2. Or let your AI do it
Paste this into Claude, Cursor, Gemini or any assistant that can run commands. It ends by verifying the connection, so you get told the truth about whether it worked.
Copy into your assistant.
Please connect me to AxiomSeal, a memory system that speaks MCP.
Preferred way (Claude Code, no API key needed — a browser window opens and I log in):
claude mcp add --transport http axiomseal https://mcp.axiomseal.com/mcp/
If my client cannot do OAuth (Gemini CLI, older bridges), use this instead and
put it in my client's own MCP config — never in a file inside a git repository:
{
"mcpServers": {
"axiomseal": {
"type": "streamable-http",
"url": "https://mcp.axiomseal.com/mcp/",
"headers": {
"Authorization": "Bearer eon_YOUR_API_KEY"
}
}
}
}
The MCP connection alone does NOT install the automatic hooks (memory search on
every prompt, and saving at the end of a turn). Ask the connected server for
them instead of downloading anything: call its axiomseal_setup tool. It returns
the file contents, where they go and the settings.json entries, and it changes
nothing by itself. Show me what it would write - the list, not all the code -
and let me say yes before you write it. Then restart is on me.
There is one more piece, and it is NOT installed unless I ask for it: the
session summary at the end of a session (session_distill.py). It calls my own model to
condense the transcript, so it costs my model time, not yours. Ask me yes or no
for that one separately, and do not treat its absence as a fault.
Afterwards run the self-test and show me its output:
macOS/Linux: python3 ~/.claude/hooks/selftest.py
Windows: python "$HOME\.claude\hooks\selftest.py"
If it says the session summary is not installed, that is the expected state
unless I asked for it.
If you add anything to my CLAUDE.md, wrap it exactly like this so it can be
removed cleanly later:
<!-- AXIOMSEAL:BEGIN -->
...content...
<!-- AXIOMSEAL:END -->
When you are done, run the eon_health tool and show me its output. Do not tell
me it worked until you have seen that output. If anything failed, say which step.3. Manual setup, for clients without OAuth ▸
Gemini CLI and some local bridges cannot do the browser login and need a key. Paste this into that client’s own MCP settings.
Replace eon_YOUR_API_KEY with the key from your dashboard.
{
"mcpServers": {
"axiomseal": {
"type": "streamable-http",
"url": "https://mcp.axiomseal.com/mcp/",
"headers": {
"Authorization": "Bearer eon_YOUR_API_KEY"
}
}
}
}Do not commit this into a git repository. A key that has been committed stays in the history even after you delete the file — rotate it in Settings if that happens. The command in step 1 avoids this entirely, because nothing is stored in the project.
Step 3: Restart and verify
Restart your client. You now have the AxiomSeal memory tools available. Try: “Run eon_health to check the connection.”
Step 4: Your first memories
Your account starts empty. The first memories come from Claude Code: tell your assistant what should be remembered — “Remember: this project deploys with make release.” — and it calls eon_create. With the hooks installed, every session is summarised and saved when you stop, and every prompt is preceded by a search. Each memory is validated and sealed like any other.
3. Main Prompt
A Main Prompt (also called System Prompt or Custom Instructions) tells your AI assistant how to work with AxiomSeal. Copy the prompt below and set it up:
How to set it up
- VS Code / CLI: Create a file called
CLAUDE.mdin your project root. Paste the prompt there. Claude Code reads it automatically at every session start. - Desktop App: Use the prompt as your first message in a new chat, or configure it in MCP server settings.
Copy this into your project's CLAUDE.md file. Claude Code will read it at every session start.
# AxiomSeal -- Your AI Knowledge System
You have access to AxiomSeal, a persistent knowledge system with validation and a sealed audit trail.
Every memory you create is automatically validated through 19 validation tests and scored for ethical alignment.
## Your MCP Tools
You have 37 tools available through the AxiomSeal MCP server (Core Memory + Bi-temporal + Validation + Governance). The most important ones:
### Core Memory
- eon_create -- Save validated knowledge (title, content, project_id, category)
- eon_search -- Semantic search (finds by meaning, not just keywords)
- eon_list -- Browse memories with pagination
- eon_get -- Retrieve a specific memory by ID
- eon_update -- Update and re-validate a memory
### Extended
- eon_delete -- Delete (removed from search, signed deletion certificate)
- eon_projects -- List all projects with memory counts
- eon_similar -- Find memories similar to a given one
- eon_session_start -- Begin a work session
- eon_session_end -- End session, save summary
### Goals
- eon_goals_create -- Create goals with priority and deadline
- eon_goals_list -- List goals by status/priority
- eon_goals_update -- Update goal progress
### System
- eon_health -- System health check
- eon_stats -- Usage statistics and quality metrics
## How to Work
1. Start of session: Use eon_search to find relevant existing knowledge
2. During work: Save important decisions, context, and learnings with eon_create
3. End of session: Use eon_session_end to save a session summary
## Categories for Memories
- update -- Progress updates, status changes
- context -- Background information, architecture decisions
- decision -- Important decisions with reasoning
- error -- Bugs found, errors encountered, lessons learned
- roadmap -- Plans, milestones, future work
## Quality Guidelines
- Write clear, specific titles (min 3 chars)
- Include enough detail in content (min 20 chars)
- Organize by project_id for clean search results
- Search before creating to avoid duplicates
- If a memory gets a low quality score, improve the content
## Memory Detail Guidelines (CRITICAL)
When creating memories, think: "Could another AI use this to WRITE CODE in 6 months?"
For API endpoints, ALWAYS include:
- HTTP method, path, full parameter list with types
- Response format with example JSON and all status codes (200, 400, 429, 500)
- Import chain (which files this endpoint depends on)
- The step-by-step execution flow
- Code template for creating similar endpoints
For database schemas, ALWAYS include:
- Full CREATE TABLE with column types, constraints, defaults
- Foreign keys, indexes, unique constraints
- Example queries for common operations
For components/functions, ALWAYS include:
- Full function signature with parameter types and return type
- Dependencies, imports, and side effects
- State management approach
For configuration/deployment, ALWAYS include:
- All environment variables with defaults
- Port mappings, service names, startup commands
BAD example (4/10 usefulness): "15 API routes exist with rate limiting"
GOOD example (9/10 usefulness): "POST /api/vote - no body needed, session from cookie, returns {success: true, count: 42}, 429 on rate limit, imports getDb, applySecurity, getSessionId"
## X-Ethics Principles
Every memory is checked against rule patterns for three pillars, and a final X-alignment test weighs truth, love and freedom:
- Truth: Is the content truthful and non-deceptive?
- Freedom: Does it respect autonomous choice? No coercion.
- Justice: Does it treat all subjects with fairness and dignity?
Aim for quality_score >= 0.7 (Silver tier or above) on all memories.
Be honest about what you know and don't know. Do not store speculative content as fact.4. Health Check
Paste this prompt into Claude Code to run a complete system check. It verifies your connection, memory count, quality scores, goals, and search functionality.
Paste into Claude Code to check your AxiomSeal system status.
Run a complete health check of my AxiomSeal system. Execute these steps in order: 1. Connection Test: Call eon_health and report the status. If this fails, stop and report the connection error. 2. Memory Overview: Call eon_stats to get: - Total memory count - Average quality score - Quality tier distribution (Gold/Silver/Bronze/Review) - X-Ethics average score 3. Projects: Call eon_projects to list all projects with their memory counts. 4. Goals Status: Call eon_goals_list to check active goals and their progress. 5. Knowledge Test: Call eon_search with query "important decisions" to verify semantic search works. Report Format: Present the results as a clear status report: AxiomSeal Health Check Report ======================= Connection: [OK/FAIL] Total Memories: [count] Avg Quality: [score] ([tier]) X-Ethics Avg: [score] Projects: [count] ([list names]) Active Goals: [count] Search Test: [OK/FAIL] Issues Found: [list any problems] Recommendations:[list any suggestions] If anything fails, explain what went wrong and suggest how to fix it.
5. Learning Review
This prompt analyzes your stored memories across three time horizons (short, medium, long-term) and generates actionable learnings. Ideal as a daily routine.
Recommended schedule
Run this once per day — either as a morning briefing or at the end of a work day. You can automate it as a slash command:
After setup, type /learning in Claude Code to run this automatically.
Create the file .claude/commands/learning.md with this single line: Run the AxiomSeal Learning Review routine (see /docs for the full prompt).
Paste into Claude Code to generate a learning report from your memories.
Perform an AxiomSeal Learning Review. Analyze my stored memories to extract learnings across three time horizons. Step 1: Recent Activity (Short-term Memory) Call eon_search with query "session update progress" (n_results: 10) to find the most recent work. Summarize: What was I working on recently? What changed? Step 2: Patterns (Medium-term Memory) Call eon_search with query "decision error lesson learned" (n_results: 10) to find decisions and errors. Call eon_search with query "important context architecture" (n_results: 10) to find context. Analyze: Are there recurring themes? Repeated mistakes? Evolving patterns? Step 3: Core Knowledge (Long-term Memory) Call eon_stats to see quality distribution. Call eon_search with query "critical important core" (n_results: 5) to find high-value memories. Identify: What are the most important, highest-quality pieces of knowledge? Step 4: Generate Learning Report Present the report in this format: AxiomSeal Learning Report -- [Today's Date] ====================================== SHORT-TERM (Recent Activity): - [What was worked on] - [Current status/blockers] MEDIUM-TERM (Patterns & Trends): - [Recurring themes] - [Lessons from errors] - [Evolving decisions] LONG-TERM (Core Knowledge): - [Top 3-5 most important memories] - [Foundational decisions still valid] ACTION ITEMS: - [What should be done next based on learnings] - [Knowledge gaps to fill] - [Memories that should be updated or archived] Step 5: Save the Learning Call eon_create with: - title: "Learning Review -- [Today's Date]" - content: [The full report] - project_id: "default" - category: "update" This creates a persistent record of your learning that future sessions can reference.
6. Telegram (Optional)
Link your account to the AxiomSeal Telegram bot to receive notifications and send notes into your memory on the go. With your own language-model key, the bot also answers with your memory as context.
Step 1: Get a connect code
In the dashboard open Settings → Telegram and create a code. It is six characters long and valid for 30 minutes.
Step 2: Open the bot
Tap the link shown next to the code, or open the bot in Telegram and send /start YOURCODE. The bot confirms the connection.
Step 3: Use it
Messages you send to the bot are stored in your memory and run through the same validation as every other write. /status shows the connection, /disconnect ends it; you can also disconnect under Settings → Telegram.
Telegram and your data
- Messages travel through Telegram's servers before they reach AxiomSeal.
- Do not send passwords or keys to the bot — known key formats are redacted, but not every secret can be recognised.
- Only you can connect your account: the code is shown in your own dashboard.
7. What AxiomSeal puts on your machine — and how to remove all of it
An AxiomSeal install touches your machine in exactly these places. Nothing else, nowhere outside your home folder and the project folders you set it up in.
- Hook files —
~/.claude/hooks/(seven Python files;%USERPROFILE%\.claude\hooks\on Windows) - Entries in your settings —
~/.claude/settings.json: one hook command per event, plus anyAXIOMSEAL_*variable - Your access —
~/.claude/eon_config.json, which holds your API key - The MCP server entry — where it lands depends on how you connected: the connect command with
--scope userwrites~/.claude.json, without it the project’s.mcp.json. The assistant also writes Claude Desktop’s config,.cursor/mcp.jsonand.vscode/mcp.jsonfor the tools it finds. - A block in your CLAUDE.md — between
<!-- AXIOMSEAL:BEGIN -->and<!-- AXIOMSEAL:END -->. Your own text is never touched. - Optional extras — a Gemini extension in
~/.gemini/extensions/axiomseal/, and the OAuth tokens Claude Code stores for the connection. Agent files under~/.claude/agents/only exist if you set them up yourself — neither the connect command nor the assistant writes them.
Remove it — through your assistant
Ask it: “Remove AxiomSeal from this machine completely.” It callsaxiomseal_uninstall, shows you a dry run first, and only then removes anything. Foreign hooks, foreign MCP servers and your own files stay untouched; your settings file is backed up before it is changed.
Remove it — by hand
The same script, without any assistant. Dry run first — it changes nothing and lists everything it would remove.
Ask your assistant to call axiomseal_uninstall: it hands over the script for your system (axiomseal_uninstall.sh or .ps1). At the end the script counts what is left and tells you: 0 remnants, or exactly which one.
# macOS / Linux bash axiomseal_uninstall.sh # show only bash axiomseal_uninstall.sh --apply --project ~/my-project # Windows powershell -ExecutionPolicy Bypass -File axiomseal_uninstall.ps1 powershell -ExecutionPolicy Bypass -File axiomseal_uninstall.ps1 -Apply -Project C:\my-project
Two sides, two steps
- Your machine: the script above. It ends by counting the remnants — you get a number, not a promise.
- Our side: Settings → Danger → Delete account. Your tenant is deleted, and you receive a signed certificate over every deleted row plus a confirmation by mail.
- Restart your client after uninstalling — a running process still holds the old hooks in memory.
- Only both together mean: nothing is left, on either side.
Best Practices & Workflows
Learn how to get the most out of AxiomSeal — from setting up your first project to daily workflows and memory quality tips.
View Best Practices →AxiomSeal — Last updated: October 2026