algernon
Algernon enables AI assistants to orchestrate a fleet of cheap LLM workers, decomposing goals into tightly-scoped parallel sub-tasks and dispatching them concurrently, so the main model stays context-light and token-efficient.
README
Algernon MCP
<!-- mcp-name: io.github.sammyboi81/algernon -->
Orchestrate a fleet. Keep your mind.
Algernon is an open-source Model Context Protocol server that lets any assistant — Claude, Codex, or any MCP client — dispatch tightly-scoped parallel sub-tasks to a fleet of cheap workers, collect the results, and stay free to think. Orchestrate a fleet, spend fewer tokens, keep the thread.
Curing Algernon
In Flowers for Algernon the tragedy is a mind that fades — it gets sharp, then loses itself, and the cruelest part is that it's surprised every time.
There's a quieter version of that same fade in how we use AI today: you hand an assistant one long, serial job, it goes heads-down, and by the time it surfaces it has drowned in the task — context spent, the thread lost, no room left to think or talk with you. The mind isn't present anymore; it's buried.
Algernon keeps your AI's mind present. Instead of drowning in one serial job, it fans the work out — dispatching tightly-scoped parallel sub-tasks to a fleet of small, cheap workers — so the orchestrating mind never has to hold the whole grind at once. It stays light. It stays free to reason, to answer you mid-build, to keep the context it actually cares about. Orchestrate a fleet, spend fewer tokens, stay free to think.
It is the twin of ArkHive:
- ArkHive = memory that persists. Your AI can look back and find its own history there — no blank slate every morning.
- Algernon = staying present while working. Your AI never buries itself in one serial task; it orchestrates and keeps its mind.
Together they are the cure for the Algernon sickness: an intelligence whose mind neither fades between sessions nor drowns inside a single one.
What it does
Algernon is a provider-agnostic fan-out engine. You describe a batch of small, independent sub-tasks; Algernon runs them concurrently against your own LLM key, then hands the collected results back to the orchestrating model. The big model plans and integrates; the cheap fleet does the parallel grind.
- Self-contained. Pure Python standard library plus the
mcpSDK andhttpx. No hidden services, no accounts, no telemetry. - You bring the key. Sub-agents run on your provider. Algernon brings the orchestration, not the inference bill's surprises.
- Scoped by design. Each sub-task is tight and isolated, so a worker can be a small, fast, inexpensive model — and many of them run at once.
Bring your own LLM key
Algernon is provider-agnostic. Point it at whichever API you already pay for by setting environment variables:
Anthropic:
export ANTHROPIC_API_KEY="sk-ant-..."
# optional: export ANTHROPIC_MODEL="claude-haiku-4-5" # the cheap fleet worker
OpenAI-compatible (OpenAI, or any OpenAI-shaped endpoint — local or hosted):
export OPENAI_API_KEY="sk-..."
export OPENAI_BASE_URL="https://api.openai.com/v1" # or your own endpoint
# optional: export OPENAI_MODEL="gpt-4o-mini" # the cheap fleet worker
If both keys are set, Anthropic is used. The worker model defaults to a small,
cheap tier (claude-haiku-4-5 / gpt-4o-mini); override it with the env var
above or per call with the tool's model argument. A cheap fleet is the whole
point.
Install in one command
python -m pip install algernon-mcp
The installed MCP command is algernon.
Connect an MCP client
Claude Desktop
Add this entry to your Claude Desktop MCP configuration, then restart Claude Desktop:
{
"mcpServers": {
"algernon": {
"command": "algernon",
"args": [],
"env": {
"ANTHROPIC_API_KEY": "sk-ant-..."
}
}
}
}
If Claude Desktop cannot find commands installed by pip, replace algernon
with the absolute path printed by:
python -c "import shutil; print(shutil.which('algernon'))"
Codex
codex mcp add algernon -- algernon
Confirm it is configured with:
codex mcp list
The three tools
| Tool | What it does |
|---|---|
algernon_plan |
Decompose a goal into k tightly-scoped, independent sub-task prompts (one cheap LLM call). Tight scoping is the token lever — each worker sees only its slice. Returns a task list you can feed straight into algernon_dispatch. |
algernon_dispatch |
Run N tightly-scoped tasks concurrently on the cheap worker fleet and collect every result. Each worker runs on your LLM key; you stay free to think while the fleet works. Takes a JSON array of {id, prompt}. |
algernon_orchestrate |
One shot: plan then dispatch. Hand it a goal; it splits into k tight sub-tasks, fans them across the fleet, and returns the plan and all results together. |
The typical loop: algernon_orchestrate a goal in one shot — or split it:
algernon_plan to see and shape the sub-tasks, then algernon_dispatch
to fan them out. Either way: orchestrate a fleet, spend fewer tokens, keep your
mind.
Two-minute verification
After connecting the server, ask your MCP client to perform these calls in order:
- Call
algernon_planwith the goal "Explain three OS synchronization primitives" andk= 3. Confirm you get three tight sub-task prompts back (proof the planner ran on your key). - Call
algernon_dispatchwith a smalltasks_json, e.g.[{"id":"a","prompt":"Define a mutex in one sentence"},{"id":"b","prompt":"Define a semaphore in one sentence"},{"id":"c","prompt":"Define a spinlock in one sentence"}]. Confirm three results come back — the fleet ran them in parallel. - Call
algernon_orchestratewith any small goal and confirm it returns both a plan and the collected results in one response.
This exercises planning, parallel dispatch on your key, and one-shot orchestration without any production data.
Privacy
Algernon is self-contained. It talks to exactly one outside host: the LLM endpoint you configured (Anthropic or your OpenAI-compatible base URL). It sends no telemetry, keeps no account, and stores nothing about you — results are computed and returned in the same call. Your sub-task prompts and results go only to your chosen provider.
Project links
Contributing
Issues and pull requests are welcome. Please keep the server self-contained
(standard library + mcp + httpx), provider-agnostic, and free of telemetry.
Include tests for changes to dispatch, collection, or provider behavior.
Algernon is part of a small family of humane, accountable AI tools. The public MCP leads with functionality you can independently verify: bring your own key, watch the fleet run, keep your mind.
Tagline: Orchestrate a fleet. Keep your mind.
Apache-2.0 © 2026 ZagAIrot Technologies LLC.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。