find_toolsLABSCO SUMMARY
The installer is the price of admission.
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.
What it is
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.
What you get
- 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: the README says 210+ tools are registered and around 80 load immediately; the rest arrive on demand through
find_toolsandload_tool_group, the only two tools it names — setMETIS_TOOL_SEARCH=0to load them all
Requirements
One installer command rather than a paste-in config: the setup script 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. From a clone, run bash system/mcp-server/setup-mcp.sh. 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.
Setup effort
One command — bash <(curl -fsSL https://raw.githubusercontent.com/SVerITG/Metis_PH/main/system/mcp-server/setup-mcp.sh)
USE CASES
Asking a question of your own literature
Get an answer built from your indexed library with page-level citations, instead of a plausible summary.
Starting the day with what changed
Read the morning brief on your exact topics rather than scanning feeds.
Turning a meeting into something usable
Paste the transcript and get structured notes, action items, and links to the projects they touch.
Keeping context across months
Let ideas, papers and meeting notes connect automatically, so an old question resurfaces when a new paper matches it.
2 tools
Listed in project docs. Your client may show a different list.
load_tool_groupBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
bash <(curl -fsSL https://raw.githubusercontent.com/SVerITG/Metis_PH/main/system/mcp-server/setup-mcp.sh)MCP Clients
Claude Code
claude mcp add metis-rc ~/.local/share/metis-mcp/run.shClaude Desktop — macOS
{
"mcpServers": {
"metis-rc": {
"command": "bash",
"args": [
"/Users/<YOUR_USERNAME>/.local/share/metis-mcp/run.sh"
]
}
}
}Claude Desktop — Linux
{
"mcpServers": {
"metis-rc": {
"command": "bash",
"args": [
"/home/<YOUR_USERNAME>/.local/share/metis-mcp/run.sh"
]
}
}
}Claude Desktop — WSL
{
"mcpServers": {
"metis-rc": {
"command": "wsl",
"args": [
"-e",
"/home/<YOUR_USERNAME>/.local/share/metis-mcp/run.sh"
]
}
}
}