arcane
Allows importing commits from a git repository as searchable artifacts.
Allows importing CI runs from GitHub Actions to detect flake patterns and analyze velocity.
Allows importing tickets from Linear as searchable references.
Provides local embedding generation using Ollama for semantic search of memories.
Provides embedding generation using OpenAI's API for semantic search of memories.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@arcaneSave a memory about the database migration plan"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Arcane
Beta software — Arcane is in active development. APIs and storage formats may change between releases. Pin your version and back up
~/.arcanebefore upgrading.
Unified engineering intelligence — persistent memory, decision journeys, and knowledge capture for AI-assisted development workflows.
Arcane runs as an MCP (Model Context Protocol) server, giving Claude Code, Claude Desktop, and other MCP-compatible agents a persistent, searchable knowledge store that survives context window resets and spans every project you work on.
What It Does
Memories — save and search decisions, bugs, patterns, and learnings with hybrid FTS + vector search
Journeys — track multi-step investigations from problem → exploration → decision → outcome
Artifacts — ingest CI runs, git commits, and Linear tickets as searchable references
Relationships — link any entities (memory → memory, journey → artifact, etc.) into a knowledge graph
Content generation — draft blog posts and Architecture Decision Records from your stored knowledge
Intelligence — detect CI flake patterns and summarise engineering velocity
Related MCP server: Memory-MCP
Quickstart
Install
# With uv (recommended)
uv tool install arcane
# Or with pip
pip install arcaneInitialise
arcane initThis creates ~/.arcane/ with a SQLite database and default config.
Connect to Claude Code
Add to your Claude Code MCP config (~/.claude/config.json or project .claude/config.json):
{
"mcpServers": {
"arcane": {
"command": "arcane",
"args": ["mcp"]
}
}
}Restart Claude Code — Arcane tools will be available automatically.
Connect to Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"arcane": {
"command": "arcane",
"args": ["mcp"]
}
}
}MCP Tools
Once connected, Claude has access to these tools:
Tool | Purpose |
| Save a decision, bug, pattern, or learning |
| Semantic + keyword search across all memories |
| Load relevant memories for the current project |
| Fetch full details for a specific memory |
| Update a memory in place (use when a save warns |
| Remove a memory by ID |
| Begin tracking a multi-step investigation |
| Add a progress update to a journey |
| Mark a journey done with an outcome summary |
| Mark a journey abandoned (dead end or superseded) |
| Delete a journey and its relationships |
| List active or recent journeys (stale ones are flagged) |
| Import commits from a git repository |
| Import CI runs from GitHub Actions |
| Import tickets from Linear |
| Run intelligence plugins (flakes, velocity, health) |
| View and acknowledge derived insights |
| Create a relationship between two entities |
| Walk the relationship graph from an entity |
| Generate a structured blog post brief |
| Generate an ADR from a decision memory |
CLI Reference
# Memory
arcane save # Interactive save
arcane search "query" # Hybrid search
arcane context # Print context for agent injection
arcane details <id-prefix> # Full memory details
arcane delete <id-prefix> # Delete a memory
arcane reindex # Rebuild vector index
arcane stats # DB statistics
arcane sessions # List recent sessions
# Journeys
arcane journey start # Start a journey
arcane journey update <id> # Add an update
arcane journey complete <id> # Mark complete
arcane journey list # List journeys
arcane journey show <id> # Full journey with linked entities
# Ingestion
arcane ingest git # Ingest local git commits
arcane ingest gha # Ingest GitHub Actions runs
arcane ingest linear # Ingest Linear tickets
# Intelligence
arcane analyze flakes # Detect CI flakes
arcane analyze velocity # Engineering velocity summary
arcane analyze health # Store health audit — fragmentation, orphans, journey hygiene
# Content
arcane draft blog # Blog brief from memories
arcane draft adr <memory-id> # ADR from a decision memory
# Relationships
arcane link <type-id> <type-id> <rel-type> # Create link
arcane trace <type> <id> # Walk graph
# Config
arcane config # Show current config
arcane config set-home <path> # Set custom data directory
arcane config clear-home # Remove custom home setting
# Server
arcane mcp # Start MCP server (stdio)
arcane -v mcp # With debug loggingConfiguration
Config is loaded from ~/.arcane/config.yaml (or $ARCANE_HOME/config.yaml):
embedding:
provider: ollama # "ollama" or "openai"
model: nomic-embed-text # Embedding model name
base_url: http://localhost:11434 # Ollama base URL (ignored for openai)
api_key: null # OpenAI API key (or set OPENAI_API_KEY env var)
context:
semantic: auto # "auto" | "always" | "never"
topup_recent: true # Supplement semantic results with recent memories
projects:
aliases: # Merge different names for the same work into one
grafana-usage-report: grafana-usage-automation
dedup:
threshold: 0.92 # Cosine similarity that triggers a near_duplicate
# warning on save (warn-only, never blocks)Project names are canonicalized on every save and lookup: trimmed, lowercased,
separators collapsed (Edition X → edition-x), owner/repo reduced to the
repo name, then mapped through projects.aliases. To heal an existing split,
list the silos and merge them:
arcane projects # distinct projects with counts
arcane merge-projects grafana-usage-report grafana-usage-automation # dry run
arcane merge-projects grafana-usage-report grafana-usage-automation --apply # commitEnvironment Variables
Variable | Purpose |
| Override data directory (default: |
| GitHub API auth for GHA ingestion |
| Linear API key for ticket ingestion |
| OpenAI API key (alternative to config file) |
| Log verbosity: |
Semantic Search
Arcane supports two embedding backends:
Ollama (default, local, free)
# Install Ollama: https://ollama.ai
ollama pull nomic-embed-text
# Config (default — no changes needed)
embedding:
provider: ollama
model: nomic-embed-textOpenAI
# Set API key
export OPENAI_API_KEY=sk-...# config.yaml
embedding:
provider: openai
model: text-embedding-3-smallAfter switching models, rebuild the vector index:
arcane reindexMemory Categories
Category | Use for |
| Architectural or design decisions (include tradeoffs in |
| Bugs you fixed — root cause, fix, and how to recognise it |
| Reusable patterns or best practices |
| Things you discovered or figured out |
| Background knowledge about a project or system |
| Proof-of-concept or spike findings |
| Significant work shipped |
Plugin System
Arcane uses Python entry points for extensibility. Install any package that declares the right entry point and Arcane will discover it automatically.
# In your plugin package's pyproject.toml
[project.entry-points."arcane.plugins.ingestion"]
jira = "my_package:JiraIngestionPlugin"
[project.entry-points."arcane.plugins.intelligence"]
code_churn = "my_package:CodeChurnAnalyser"
[project.entry-points."arcane.plugins.content"]
changelog = "my_package:ChangelogGenerator"Plugins must implement the protocols defined in arcane.plugins.protocols.
Data Layout
~/.arcane/
├── arcane.db # SQLite database (memories, journeys, artifacts, relationships)
└── vault/
└── <project>/
└── YYYY-MM-DD-session.md # Markdown mirror of saved memoriesAll data lives in a single SQLite file — easy to back up, sync, or inspect with any SQLite tool.
Development
git clone https://github.com/dkelly/arcane
cd arcane
uv venv && source .venv/bin/activate
uv pip install -e ".[dev]"
pre-commit install
# Run tests
pytest
# Lint + format
ruff check --fix src/ tests/
ruff format src/ tests/
# Type check
mypy src/arcaneProject Structure
src/arcane/
├── cli/ # Click CLI — one module per command group
├── domain/ # Pydantic domain models
├── infra/ # DB repos, config, search, embeddings, redaction
├── mcp_server/ # MCP stdio server + tool handlers
├── plugins/ # Plugin protocols + built-in implementations
└── services/ # Business logic layerSee AGENTS.md for detailed contributor and agent guidance.
License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Edition-X/arcane'
If you have feedback or need assistance with the MCP directory API, please join our Discord server