Phaedrus
Research-feed MCP server: literature-watch findings, watchlist, and revenue-candidate drafts.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
https://github.com/qompassai/phaedrus/releases/download/v0.1.0/phaedrus-mcp-0.1.0-linux-x64.mcpbDocumentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Phaedrus
An MCP server for the research feed: a curated literature-watch findings store and watchlist, plus a one-way, draft-only revenue seam into lupin (the revenue-alignment server, which owns its own ledger).
Phaedrus is a single Rust binary. It speaks MCP over stdio (NDJSON JSON-RPC) to the client and works on plain files under a data root — no database, no network listener.
How it runs
- Data root (findings store, watchlist, scan inbox):
--root <path>or theRESEARCH_ROOTenvironment variable (default~/workspace/research-feed-20261019). - Lupin root (read-only — capability context and draft generation):
--lupin-root <path>orLUPIN_ROOT(default~/workspace/revenue-alignment-20261019). - Writes are deliberately narrow:
research_submitfiles a candidate into the scan inbox and never touches the curated store, andrevenue_candidate_draftonly drafts a lupinopportunity_submitpayload — this server never writes lupin's files.
Tools
| Tool | What it returns |
|---|---|
capability_context | Lupin's capability registry (read-only) as planning vocabulary: capability ids + names, optionally keyword-filtered |
feed_summary | Counts: findings by system/kind, systems watched, parse health |
finding_get | One curated finding by id |
finding_list | Curated findings, optionally filtered by system |
research_submit | File a candidate (finding, roadmap item, or test proposal) into the scan inbox; never writes the curated store |
revenue_candidate_draft | A draft lupin opportunity_submit payload for a revenue-shaped finding (drafts only) |
watchlist_list | The watchlist (per-system venues and terms) |
Client config
{
"mcpServers": {
"phaedrus": {
"command": "/path/to/phaedrus",
"args": []
}
}
}
Registry
server.json in this repo is the MCP Registry record for
ai.qompass/phaedrus. The server is distributed as an MCPB bundle
attached to the GitHub releases (Linux x64).
License
Apache-2.0 — see LICENSE.
Frequently asked questions
What is Phaedrus?
Research-feed MCP server: literature-watch findings, watchlist, and revenue-candidate drafts.
How do I install Phaedrus?
Follow the installation steps in its documentation, shown on this page and in its repository.
Does Phaedrus need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Phaedrus open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains Phaedrus?
It is published by qompassai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.