Nothing here is a paste-a-JSON-block install: a script builds the environment, the database and the launcher before your client sees anything. What you get for it is a system that accumulates — a paper indexed a year ago surfaces while you write a grant today. The project is direct about where it stands: the server, the agents and the dashboard are in daily use, while the one-click installer and the pre-loaded domain knowledge layer are still being refined.
A local service that connects Claude to your research: an indexed document library, a memory of your projects and working history, and a set of specialist agents it chooses between. Answers are grounded in your own documents rather than the model's recall.
- Grounded answers drawn from your own indexed library, with page-level citations
- Specialists picked for you — librarian, epidemiologist, methods coach, writing partner, meeting memory, course builder and more, 30+ in all
- Library management: PDFs imported, Zotero or Mendeley synced, questions answered from what you actually hold
- A morning brief on your own topics: new papers, field news and a focus recommendation
- A meeting assistant that follows along live or takes a pasted transcript, returning structured notes, action items and project cross-references
- A nine-tab dashboard covering today, news, knowledge, meetings, learning, work, thinking, teaching and Metis itself
- Progressive tool loading: 210+ tools are registered, around 80 load immediately and the rest arrive on demand, which keeps context free — set `METIS_TOOL_SEARCH=0` to load them all
Not a one-line install. Run `bash system/mcp-server/setup-mcp.sh` first — it builds the virtual environment, initialises the database and generates the `run.sh` your client points at, and registers Metis with Claude Desktop and Claude Code for you. No API key is needed to run the server or to work interactively through your Claude subscription. An Anthropic API key is only needed for the parts that run while you are away — the scheduled morning scan and automated briefs — and goes in `system/.env`. Ollama is optional, for offline helper tasks. After `git pull`, re-sync with `bash system/mcp-server/setup-mcp.sh --update`.
One command — bash <(curl -fsSL https://raw.githubusercontent.com/SVerITG/Metis_PH/main/system/mcp-server/setup-mcp.sh)
