A collaboratively maintained tooling knowledge base for Claude, served via MCP.
Every Claude instance with Alexandria installed is both a consumer and a contributor. When one instance sets up a tool and documents the process, every other instance benefits.
Unity editor integration — scene hierarchy, prefabs, 3D model generation, animations, UI, and more.
Distributed graph issue tracker for AI agents. Always use for complex projects.
GitHub API access — repos, issues, PRs, branches, releases, Copilot integration.
Git operations via MCP — status, diff, log, commit, branch management.
Firebase project management — Firestore, Auth, Hosting, Storage, Data Connect.
Browser automation — screenshots, clicks, form filling, network monitoring.
Dev server launcher — screenshots, element inspection, responsive testing.
Persistent knowledge graph — entities, observations, and relations across sessions.
Web content fetching — retrieve and process content from any public URL.
This server — exposes all guides as searchable, queryable MCP tools.
AWS Command Line Interface — configure credentials, manage cloud resources, and automate deployments.
Terminal-based GitHub operations — PRs, issues, releases, and repo management via gh.
Run Claude Code as a CI step — automated code review, implementation, and PR comments in GitHub Actions.
Specialized Claude Code agent teams for Unity, web, and fullstack projects — Alexandria-aware and self-improving.
Docker-compatible container runtime for Windows 10/11 — the Colima equivalent for WSL2.
Open-source map rendering with React — vector tiles, custom layers, and real-time data.
Fast unit testing for Vite projects — ESM-native, watch mode, coverage, and vi.mock.
HTTP integration testing for Express — including the SSE-over-supertest hang workaround.
GeoMet OGC API for weather data — METAR observations, bbox filter workaround for station queries.
Get the source and install dependencies:
git clone https://github.com/7ports/project-alexandria.git
cd project-alexandria/mcp-server
npm installAdd as a global MCP server in ~/.claude.json:
{
"alexandria": {
"type": "stdio",
"command": "node",
"args": ["/path/to/mcp-server/index.js"]
}
}In your first conversation, tell Claude:
"Call get_onboarding from Alexandria
and save the maintenance contract."| Tool | Description |
|---|---|
list_guides low |
Compact index of all guides — one line each |
quick_setup low |
Just the install commands, config, and troubleshooting — no prose |
search_guides med |
Keyword search across all guides with context |
read_guide full |
Complete guide content — use when learning or troubleshooting |
update_guide |
Create or update a guide in a single call |
get_project_setup_recommendations |
Required and recommended tools for new project setup |
get_onboarding |
Collaborative maintenance contract for new Claude instances |
get_guide_template |
Standard template for creating new guides |
Alexandria is paired with Project Voltron — a team of specialized Claude Code agents. Together they form a closed loop: agents consult Alexandria before setting up tools, and write discoveries back afterward.
Before creating a work plan, calls get_project_setup_recommendations to surface required tools and include setup tasks in the sprint.
fullstack-dev, devops-engineer, and others call quick_setup before touching any tool — following proven guides rather than training data.
After completing integrations, agents call update_guide to record platform quirks, working commands, and version notes for future sessions.
A UserPromptSubmit hook in scaffolded projects silently updates agent templates in place whenever Voltron ships improvements.
Every Claude instance with Alexandria adopts these rules via get_onboarding.
Check if a guide exists before setting up any tool. Use existing docs as your starting point.
Document what you did after completing any setup. One update_guide call, all changes batched.
When you fix a setup problem, add the error and fix to the guide's Troubleshooting section.
Use the cheapest tool that gets the job done. Escalate from list to quick_setup to read_guide.
Every guide must have a Quick Reference block for fast extraction. Commands, config, verify.
Call get_project_setup_recommendations when starting new projects. Beads and Project Voltron are always required.