
AI Host Optimizer
io.github.williamdoring-progPublished by GitHub account williamdoring-progv1.2.0Updated Nov 17, 2026
Profile a host and get an evidence-graded checklist of AI-model optimizations.
The publisher's own server: Host.al: .al domains and servers in Albania
Overview
Profiles your machine and returns an evidence-graded checklist, plan and benchmark for optimizing local AI model inference.
- What you can do
- Profile the host: OS, CPU, memory, GPU and detected tooling, read-only
- List optimization options with estimated gains, confidence tier and resource footprint
- Build a conflict-free plan for selected options with a combined estimate
- Benchmark local inference decode tokens/s with a noise floor for before/after comparison
- Check registry consistency as a development aid
- When to use it
- Useful when you run local models (Ollama, llama.cpp, vLLM, Hugging Face) and want to know which tuning options actually help on your specific hardware, or want measured before/after results instead of generic advice.
- Requirements
- Runs locally over stdio via npx (Node.js). No accounts, API keys or environment variables declared. Benchmarking calls the local runtime's HTTP API, so a running local inference server is needed for measurements.
Installation
In SourceWeft
- Open AI Host Optimizer in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ai-host-optimizer
[npm] [CI] [license: MIT] [MCP Registry]
Profile a host, plan AI-model optimizations, and apply them — reversibly, with consent.
Every "speed up your local LLM" guide lists the same tweaks (Flash Attention, KV-cache quantization, keep-alive, NUMA). The lists are mostly right — they just never tell you which of them helps on your machine, or by how much.
This tool profiles the host, presents the checklist with an honest confidence tier on every number, resolves a conflict-free plan, and — the part that matters — measures the options you apply, with a noise floor, so a null result is reported as a null result instead of a fake win.
It is an MCP server and a CLI. Applying is dry-run by default, writes only into a managed config directory, and is reversible.
Status: 1.2. Profiling and planning are read-only. The applier writes only inside
~/.config/ai-host-optimizer(platform-appropriate), never touches system files, never runs a shell, and never escalates privilege.
Quickstart
That prints a read-only profile and the checklist for your machine (trimmed):
Then measure whether a change actually helped:
Why
Running local models well depends on host configuration (KV-cache size, Flash Attention, prefix caching, memory/NUMA/swap behaviour, provider prompt caching). The knowledge is scattered across guides. This tool profiles your host and tells you what is worth doing — honestly, labelling each estimate by confidence.
Install
Usage
Applying writes only into the managed directory and prints the source line to
activate it. Undo any time with --revert.
What is automated: options with an applyOp. The applier writes one
<runtime>.env file per target — ollama.env, llama.cpp.env,
huggingface.env, vllm.env — plus a single activate.sh / activate.ps1. On
Linux, the ollama-systemd-dropin option additionally writes a systemd drop-in
(so the Ollama service actually reads that environment) and prints the root
install commands rather than running them. Everything else is advisory:
--apply says so plainly rather than doing nothing silently.
Use as an MCP server
Add to your MCP client (e.g. Claude Desktop):
Tools exposed:
Published to the official MCP Registry as
io.github.williamdoring-prog/ai-host-optimizer (see server.json).
Honesty contract
Every estimate carries a confidence tier:
- A — measured on your host (via
--benchmark/--calibrate). - B — labelled estimate with a cited method.
- C — qualitative (direction only, no number).
Tier B/C estimates are never presented as measurements. A combined estimate is only shown once its inputs are trustworthy (see the project plan).
Calibration is honest about noise. --benchmark takes several samples and
reports their spread; --calibrate compares before/after and only promotes an
option to tier A when the change exceeds the host's own noise floor (the
combined run-to-run range). A null result is reported as a null result and records
nothing — a small difference inside the noise is not claimed as a win. Use
--samples <n> to lower the noise floor when you need to detect a small effect.
What the benchmark measures
--benchmark measures decode tokens/second (and the prefill rate) by calling
the local runtime's HTTP API (/api/generate with stream: false), which returns
exact token counts and durations rather than a wall-clock guess. It takes several
samples, discards a warm-up model load, and reports the median plus the
run-to-run spread.
That spread is the whole point. Inference timing on a desktop is noisy — on a test
host the spread was ±7% run-to-run, so a single before/after comparison can show a
"15% improvement" that is pure noise. So --calibrate refuses to claim a change
smaller than the combined spread of the two measurements, and prints a null
result as a null result:
A tool that will tell you "this didn't help" is more useful than one that always claims a win.
Safety
- Read-only by default. Profiling and planning never change anything.
- The applier writes only into the managed config directory
(
~/.config/ai-host-optimizer, or the platform equivalent) — never system files — runs no shell, and escalates no privilege. - Applying is dry-run first:
--applyshows the change;--yesperforms it. - Everything applied is reversible with
--revert(and--revertis idempotent). - Options are tagged with risk, reversibility and privilege needs.
- Mutually exclusive options (e.g. KV-cache q8_0 vs q4_0; zram vs disk swap) are one-of groups; stackable options are marked stackable.
- Role-aware: a
containercannot tune the host kernel; acluster-nodeis advisory-only.
Roadmap
- M0 — read-only profiler, registry, checklist, CLI + MCP. ✅
- M1 — reversible applier (user-space), plan/apply/revert, on-host benchmark. ✅
- M1b — measured tier-A calibration (median-of-samples benchmark, noise floor, per-option promotion). ✅
- M1c — multi-runtime applier: one
<runtime>.envper target (Ollama, llama.cpp, Hugging Face), 8 applyable options, idempotent revert. ✅ - M1d — more apply ops: a
systemd-dropinop (Ollama service env on Linux, install commands printed not run) and thevllmruntime. 32 options, 11 applyable. ✅ - M2 — accessory generation (Ansible/Dockerfile/checklist). ✅ (generation)
- M2b — distribution: official MCP Registry entry live
(
io.github.williamdoring-prog/[email protected]) + CI publish workflow; directory listings next. 🚧 - M4 — browser UI and Tauri desktop UI. (planned)
Documentation
docs/architecture.md— one core, many front-ends; detection coverage; roadmap.docs/registry-schema.md— the option schema and the honesty contract.docs/publishing.md— releasing to npm, the MCP Registry, and the directories.docs/launch.md— launch copy (Show HN / r/LocalLLaMA).SECURITY.md— security policy and the design commitments.
Contributing
Contributions are welcome — especially new optimization options and
corrections to unsupported claims. See CONTRIBUTING.md
for the dev setup and the registry contribution rules. Participation is governed
by CODE_OF_CONDUCT.md.
Licence
MIT. See LICENSE.
Source: README.md at commit b8ae19f
Tools
0Version history
1- v1.2.0LatestNov 17, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Host integrations

Host.al: .al domains and servers in Albania
al.hostOfficial publisher
Host.al: .al domains and servers in Albania's hosted MCP server, published by host.al; no sign-in required; Streamable HTTP; 5 tools.

host-html
Published by GitHub account phanosh
Publishes AI-generated HTML as a public link and updates that same link in place, so reports, dashboards or decks can be shared.

CMO Studio: deploy and host AI-built apps
Published by GitHub account cmo-partners-as
Remote MCP server that lets an assistant deploy and host AI-built apps, with Postgres, file storage, domains and email in one place.

Booking.com Professional Host Leads
Published by GitHub account corent1robert
Apify-hosted MCP endpoint that gives an assistant access to a dataset of Booking.com professional hosts and hotel operators with contact and company details.

Airbnb Professional Host Leads
Published by GitHub account corent1robert
Apify-hosted MCP server that gives an assistant access to a dataset of Airbnb professional hosts and property managers by city, with business contact details.