Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/automagik-dev/genieInstalling this writes the configuration, not the program: `mikro` has to be on your PATH already, or the server will not start.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/automagik-dev/genie/claude-code-mikro)<a href="https://agentmods.dev/mcp/automagik-dev/genie/claude-code-mikro"><img src="https://agentmods.dev/badge/mcp/automagik-dev/genie/claude-code-mikro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/automagik-dev/genie/claude-code-mikro"><img src="https://agentmods.dev/badge/mcp/automagik-dev/genie/claude-code-mikro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mikro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"mikro": {
"command": "mikro",
"args": [
"mcp",
"--dir",
"${CLAUDE_PROJECT_DIR}"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 10 lines scan A 043414ba6c50
mikro is an MCP server published in the GitHub repository automagik-dev/genie (346 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-16.
Other mcp servers, from other repositories
tree-sitter
MCP server "tree-sitter" as configured in FlorianBruniaux/ccboard. Launched with mcp-server-tree-sitter.
atomicmemory
MCP server "atomicmemory" as configured in atomicstrata/atomicmemory. Runs locally from the atomicmemory-mcp npm package. Needs 7 environment variables to run.
ruflo
Ruflo - Enterprise AI agent orchestration platform. Deploy 60+ specialized agents in coordinated swarms with self-learning, fault-tolerant consensus, vector memory, and MCP integration. Runs locally from the ruflo npm package. Needs 3 environment variables to run.
vectorlane
Open-source local vector memory engine for AI agents — ingest documents, chunk content, generate embeddings, search locally, return metadata/citations. Runs locally from the @talocode/vectorlane npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.