agent-julia
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., "@agent-juliasearch my memory for the project roadmap from last week"
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.
agent-julia
One brain for your AI — the same memory and persona across Claude Code, Cowork, and Dispatch.
agent-julia is a local-first MCP server that gives your AI assistant a single, persistent memory you own (plain markdown in a git repo) plus a configurable persona (name, gender, language, style). It stays small in the model's context — only a compacted, token-budgeted core is injected — while the full knowledge base lives on disk, indexed for fast full-text and semantic search.
Status: early development (pre-v0.1). Not yet published.
Why
CLAUDE.md and long context are a constant token tax, and models degrade as context grows ("context rot").
Memory is fragmented across Claude surfaces (Code, Cowork, Dispatch) and trapped per-project.
agent-julia keeps one clean, owned, versioned memory consistent everywhere, and does its own housekeeping.
Related MCP server: SafeFlo
Features (planned v0.1)
Local-first memory: markdown + git, human-readable, portable, private.
Fast search: full-text (SQLite FTS5) + semantic (embeddings).
Persona engine: name / gender / language / style preset, plus learned voice corrections.
Budgeted context injection to fight context rot.
Automatic maintenance (re-index, dedupe, compaction) + optional interactive weekly review.
Adopts an existing markdown knowledge base (not just fresh installs).
Backward-compatible upgrades with automatic data migrations.
What setup does
The onboarding wizard (agent-julia init) does three things, not one. Registering the MCP server alone is not enough — the persona and the "use your memory" instruction must be present in each surface's startup context, because the model reads those before anything else.
Registers the MCP server in your Claude clients:
Claude Desktop "Local MCP servers" config -> covers Cowork and Dispatch.
~/.claude.json(user scope) -> covers Claude Code.
Injects a small persona + usage core into each surface's startup instructions, inside a managed, clearly marked block (backed up first, idempotent, reversible on uninstall):
Claude Code: writes the block into
~/.claude/CLAUDE.mddirectly.Cowork: generates the block and guides you to paste it into Settings -> Cowork -> Global instructions (this field is app-stored, not a file), and keeps an on-disk mirror so it can be audited and re-synced.
Configures your persona and memory: name, gender, language, style preset (shown by example), memory directory, search mode.
The startup core stays tiny on purpose (persona + "use agent-julia for memory"); everything else lives in your memory base and is pulled in on demand and within a token budget.
Configuration
Name and gender are configurable — the default persona is "Julia" (she/her), but you define your own agent's identity, language, and style during setup.
Install
TBD — published to npm at v0.1.
License
MIT
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
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/elninopl/agent-julia'
If you have feedback or need assistance with the MCP directory API, please join our Discord server