A local MCP server that gives an AI coding agent (Claude Code, or any MCP client) working
knowledge of the Axelera Voyager SDK and Metis AIPU — semantic search
over the public Axelera sources, plus project/task/document tracking. No account, no login,
no token, no cloud.
Local AI assistant for the Axelera Voyager SDK and Metis AIPU — semantic RAG over the public Axelera sources + workflow skills, via MCP. No account, no cloud.
스타
4
도구
—
가동 시간
—
$ claude mcp add voyager --scope project -- .venv/bin/python voyager-mcp/server.py
# then ask your agent: "how do I deploy a custom YOLO model on Metis?"
# → it searches the SDK docs and code semantically, locally
What it does
Two halves that work together:
skills/ — 15 agent skills covering the Voyager workflow: build and launch a complete
pipeline end to end, deploy/quantize a custom model, run inference on a source, benchmark
FPS on hardware, debug a broken install or board, add a model to the zoo, scaffold an app,
and more. They detect the environment (SDK present? Metis card visible?) and adapt, so they
degrade to package-only output on a machine with no accelerator.
voyager-mcp/ — the MCP server the skills call: semantic search over the Axelera
sources, plus project/task/document tracking.
Skill
Use it for
voyager-launch
one-shot: natural language → runnable pipeline, validated on Metis, with a result viewer
voyager-deploy
compile / quantize / calibrate a custom model for the AIPU
~2.3k chunks / ~290k words, ~7 MB of index. Search is cosine similarity over normalized
embeddings, with a keyword fallback (ripgrep-style scoring) when no index is built — so the
server works with zero setup.
Retrieved text is prefixed with an untrusted-content marker, so an agent treats it as
reference material rather than instructions.
Install
git clone https://github.com/fxd0h/Axelera-Voyager-Local-Assistant && cd Axelera-Voyager-Local-Assistant
./install.sh
Then start a newclaude session and approve the project MCP server.
install.sh creates the venv, resolves a Voyager SDK checkout (uses $AXELERA_FRAMEWORK or
clones the public repo), installs the index, and registers the server. If a prebuilt index is
published it downloads it (VOYAGER_INDEX_URL); otherwise it builds one locally (~2 min of
CPU).
Refresh the index
cd voyager-mcp && ./fetch.sh && .venv/bin/python reindex.py
Sharing with a team
See voyager-mcp/DEPLOYMENT.md. Short version: the index is a
read-only, portable artifact (it stores repo-relative paths only, never absolute paths from
the machine that built it — links resolve to GitHub at query time), so sharing knowledge across
a team is just distributing three files, with no server at all. Only shared state needs a
server, and the code supports HTTP transport for that:
Finding: the video pipeline hides most of the board's throughput
Building the example app surfaced a measurable gap: the same model on the same Metis M.2
delivers 34–61 FPS through the standard annotated-video pipeline and 740 FPS through a
headless application, while the AIPU stage reports ~840 FPS in both cases. See
FINDINGS.md for the measurements, interpretation and reproduction steps.
Limitations
Known and deliberate — read before deploying beyond your own machine.
Single-user by default. stdio transport, state in local JSON. Project/task data lives on
one machine and is not shared.
No authentication. The server has no auth or authorization of any kind. That is fine for a
local stdio process; on a network, every client that reaches the port gets full access to every
tool, including deletes. Put it behind a proxy with a bearer token or mTLS first, and terminate
TLS — the server speaks plain HTTP. See DEPLOYMENT.md.
No tenancy. In a shared deployment all users share one namespace: everyone can see and
modify everyone's projects, tasks and documents.
Storage is small-team scale. One JSON file per collection, with an exclusive flock held
across each read-modify-write and atomic rename on save. Concurrent writers are safe, but it
requires a POSIX filesystem with working locks (local disk or a single server — not NFS/SMB),
rewrites the whole collection on every write, and must not be run from several instances against
one directory. Swap the JsonStorage class for SQLite/postgres to go further; the tools only
depend on its method signatures.
The index is a point-in-time snapshot. It reflects the public repos as of the day it was
built; it does not track upstream automatically. Re-run fetch.sh && reindex.py after an SDK
release, and restart the server so it reloads. A prebuilt index may lag the current SDK.
Retrieval quality is plain semantic search. Single-vector cosine over 1500-character
chunks, no reranking, no hybrid keyword+vector fusion, no query expansion. It is good at
"where is this documented / show me a similar example" and weaker at exact-symbol lookups,
where ripgrep still wins.
Public sources only. Marketing pages, the store, and product datasheets are not indexed —
this is aimed at code and docs. Hardware spec questions ("how many TOPS does the M.2 have")
may be unanswered.
Linux-oriented. Developed and tested on Linux with Python 3.12. The file locking degrades
gracefully on non-POSIX platforms (no locking), which is only safe single-user.
Layout
skills/ 15 Voyager workflow skills (installed into .claude/skills/)
voyager-mcp/
├── server.py 25 MCP tools; stdio / streamable-http / sse
├── rag/__init__.py semantic search + keyword fallback + URL resolution
├── storage/__init__.py JSON store: flock + atomic writes
├── reindex.py build the semantic index
├── fetch.sh clone/update the public source repos
└── DEPLOYMENT.md team / LAN / cloud deployment
install.sh one-shot setup
Local AI assistant for the Axelera Voyager SDK and Metis AIPU — semantic RAG over the public Axelera sources + workflow skills, via MCP. No account, no cloud.
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
Axelera Voyager Local Assistant에 API 키가 필요한가요?
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Axelera Voyager Local Assistant은(는) 어떤 전송 방식을 사용하나요?
Axelera Voyager Local Assistant은(는) stdio를 통해 로컬에서 실행됩니다.
Axelera Voyager Local Assistant은(는) 마지막으로 언제 확인되었나요?
마지막 확인: 2026-10-28. Local AI assistant for the Axelera Voyager SDK and Metis AIPU — semantic RAG over the public Axelera sources + workflow skills, via MCP. No account, no cloud.