Minerva
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., "@Minervacheck stack readiness"
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.
Minerva
Agent library operator and stack readiness CLI/MCP for the shared ~/.agents tree.
Minerva manages skills and profiles on disk (the same layout local-agent loads), and probes companion tools (bob, cortex, mcphub, codemap, vecgrep, …) using real binary names and tiered health.
It is not a second agent runtime, not Cortex, and not MCPHub. Skill “activation” updates Minerva-local state only; local-agent injects skills via profiles, /skill, and load_skill.
Built with Go + Cobra + MCP stdio (same family as Bob / Cortex).
What Minerva does
Surface | Role |
Skills | Create/list/show/compare/delete under |
Profiles | Create/list/show/update/delete |
Templates | Seed profiles with role prompts + skill bundles |
Stack check | Presence probe (correct binaries, core vs optional tiers) |
Stack deep | Bob/cortex/mcphub + readiness doctors/status |
Suggest | Ranked library/stack suggestions (one engine for CLI + MCP) |
Analytics | Append-safe Minerva-local event log |
MCP | Expose the above over stdio for harnesses / MCPHub |
Related MCP server: Taproom
Quick start
Prerequisites
Install / build
# Homebrew (recommended for macOS and Linux)
brew install --cask abdul-hamid-achik/tap/minerva
# From source
task build # bin/minerva
# or
go install github.com/abdul-hamid-achik/minerva/cmd/minerva@latestInitialize
minerva initCreates:
~/.agents/
agents/ # agent profiles (agent.yaml)
skills/ # skill definitions (SKILL.md)
templates/ # disk role templates (override builtins)
tasks/ # reserved
memories/ # reservedOverride root with MINERVA_AGENTS_DIR (tests should always use this).
CLI
Skills
minerva skill list
minerva skill show <name>
minerva skill compare <a> <b>
minerva skill create <name> [content] [-d description] [--from-file path]
minerva skill update <name> [-d description] [--content body|--from-file path]
minerva skill activate <name> # Minerva-local catalog pin only
minerva skill deactivate <name>
minerva skill delete <name>Profiles
minerva profile list
minerva profile show <name>
minerva profile compare <a> <b>
minerva profile create <name> [prompt] [-d desc] [-m model] [-s skill]...
minerva profile update-prompt <name> <prompt>
minerva profile update-skills <name> skill1,skill2 # replace
minerva profile add-skills <name> skill1,skill2 # merge (durable SSOT)
minerva profile remove-skills <name> skill1,skill2
minerva profile update-model <name> <model>
minerva profile update-mcp <name> server1,server2
minerva profile update-desc <name> <description>
minerva profile delete <name>Status / doctor
minerva status # unified library + presence + deep + evidence + next
minerva doctor # alias
minerva status --json
minerva status --require-retrieval
minerva status --watch --interval 30sStack
minerva stack check # presence, tiered; exit 1 if core missing
minerva stack check --json
minerva stack check --strict # also exit 2 when optional tools missing
minerva stack deep [workspace]
minerva stack deep --json
minerva stack deep --stash # save report to fcheap (minerva-stack, TTL 30d)
minerva stack deep --require-retrieval # exit 3 if retrieval not ready
minerva stack deep --require-core # exit 1 if core presence incompletestack deep sets retrieval_ready only when both codemap and vecgrep are domain-ready (indexed, not stale). Binary-on-PATH is not enough.
MCPHub slice includes unused_enabled servers and harness agents_drift from mcphub status --json. Suggest will propose mcphub disable <server> for zero-call enabled servers and flag profile mcp_servers that name unknown hub servers.
Cortex slice uses cortex overview --json (sessions/active/stale/verified rates) plus sample stale sessions and active count for the current workspace. Suggest surfaces stale backlog and low verified rates — it never mutates cortex tasks.
Binary map (product → PATH command):
Product | Binary | Tier |
bob |
| core |
cortex |
| core |
mcphub |
| core |
codemap |
| core |
vecgrep |
| core |
fcheap |
| core |
monitor |
| optional |
hitspec |
| optional |
glyphrun |
| optional |
cairntrace |
| optional |
vidtrace |
| optional |
tinyvault |
| optional |
veclite |
| infra |
Core missing → unhealthy. Optional missing → degraded only.
Suggest / analytics / templates
minerva learn
minerva skill resolve "review this PR"
minerva suggest
minerva suggest --json
minerva suggest --apply # allowlisted profile add-skills actions
minerva suggest --apply-local # also Minerva-local skill activate
minerva analytics
minerva template list|show|apply|install|save
minerva library export|import|lint
minerva bridge show <profile>Evidence (fcheap tags)
Durable outcomes go through fcheap with standard tags — Minerva does not reimplement the vault.
minerva evidence docs
minerva evidence save ./run-artifacts --kind eval --outcome pass \
--tag skill:qa-tester --tag profile:code-reviewer --index
minerva evidence search minerva-eval
minerva evidence close <stash-id> --note "fixed"
fcheap list --tag minerva --tag outcome:fail --jsonTags always include minerva; kind adds minerva-eval / minerva-suggest / minerva-stack / minerva-incident; optional outcome:pass|fail|skip.
Attribution: skill:<name>, profile:<name> — minerva suggest reads failed stashes for evidence-backed recommendations.
MCP
minerva mcp serveNine read-only tools: minerva_learn, minerva_status, minerva_suggest, minerva_resolve_skill, minerva_skill, minerva_profile, minerva_library, minerva_stack_check, minerva_evidence. Mutations stay on the CLI.
Wire via MCPHub:
servers:
minerva:
command: minerva # or absolute path to bin/minerva
args: [mcp, serve]
enabled: trueFor local-agent, list exact trust routes (no wildcards). Prefer read-only tools in AUTO; gate mutations.
Architecture
cmd/minerva/
internal/
cli/ Cobra commands
mcp/ MCP stdio server
skill/ Skill discovery + Minerva activation state
profile/ Profile YAML management
templates/ Role prompt templates
monitor/ Presence probes (bins + tiers)
integration/ Deep readiness (sibling CLIs)
suggest/ Shared suggestion engine
analytics/ Append-safe event store
version/Contracts with local-agent
Shared (disk SSOT):
~/.agents/skills/*/SKILL.md~/.agents/agents/*/agent.yamloptional
agents.md/instructions.md
Not shared:
~/.agents/.minerva-skills.json— Minerva activation only~/.agents/.minerva-analytics.json— Minerva analytics only
local-agent projects profile skills into session Active Skills at startup; it never reads Minerva activation state.
Do not reimplement
MCPHub gateway/sync/telemetry · Cortex task lifecycle · Bob plan/apply · Codemap graph · Vecgrep index · fcheap vault · glyph/cairn runners · tvault secrets · monitor process ops
Minerva orchestrates their public --json surfaces.
Development
task build
task test
task lint
task fmt
task glyph-fast # Glyphrun CLI self-specs (fast)
task glyph # includes slow stack deep retrieval_ready field check
task docs:dev # VitePress site → http://127.0.0.1:5173
task docs:build # static site → docs/.vitepress/dist
task cairn # browser specs against local docs
task cairn-prod # browser specs against https://minervacli.devCLI contracts:
specs/*.yml(glyph)Docs site:
docs/→ deploy to minervacli.dev (Vercel)Browser contracts:
browser-specs/*.yml(cairn)
Releases
See CHANGELOG.md for user-facing notes.
Tags matching v* run GoReleaser in GitHub Actions. The workflow publishes
macOS and Linux archives for amd64/arm64, creates a GitHub Release with
checksums, and updates Casks/minerva.rb in
abdul-hamid-achik/homebrew-tap.
Cross-repository publishing requires the HOMEBREW_TAP_TOKEN repository
secret with Contents read/write access to the tap repository.
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.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceCompiles skill definitions and serves them to AI agents via MCP, enabling tools for context packing, dependency resolution, and skill searching.
- AlicenseNot gradedqualityBmaintenanceDiscovers and manages portable agent capabilities (skills and MCP servers) from configurable collections, providing search, inspection, and local installation via CLI and MCP tools.1MIT
- FlicenseAqualityBmaintenanceActs as a personal AI development environment manager, enabling workspace bootstrapping, headless skill and bundle installation, global caching, and health diagnostics.731
- AlicenseNot gradedqualityBmaintenanceEnables managing local repositories, CLIs, MCP servers, and skills via MCP tools, with inventory tracking, guarded updates, and Docker-sandboxed trials.MIT
Related MCP Connectors
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.
Project management MCP for AI agents with safe task reads and writes.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/abdul-hamid-achik/minerva'
If you have feedback or need assistance with the MCP directory API, please join our Discord server