About Phaedrus
Phaedrus is a Rust MCP server for teams maintaining a curated research feed and watchlist. It reads and lists findings, accepts candidates into a scan inbox, and drafts—but does not submit—revenue opportunities for lupin.
Key features
- 01Curated finding lookup and listing
- 02Feed counts and parse-health summary
- 03Watchlist access
- 04Research candidates filed to scan inbox
- 05Draft revenue opportunity payloads
- 06Read-only lupin capability context
Use cases
- 01Review curated findings by system
- 02Submit a candidate without changing the curated store
- 03Prepare a revenue opportunity draft for lupin
MCP support
Phaedrus exposes research-feed tools to MCP clients over stdio using NDJSON JSON-RPC. Its revenue integration only reads lupin context and generates drafts; it does not write lupin files.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEPhaedrus
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.