my-lit-mcp
Related Servers
Alternatives to my-lit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables local literature workflows by searching arXiv, retrieving paper metadata, downloading and parsing PDFs, and retrieving page-cited body evidence for Q&A. It also exposes usage resources and templates for searching, analyzing, and summarizing papers via stdio MCP.4MIT
- AlicenseBqualityCmaintenanceEnables locally-first literature research through an MCP host by collecting sources, parsing documents, retrieving evidence, validating citations, and exporting research records in multiple formats.38MIT
- FlicenseNot gradedqualityDmaintenanceA local academic research assistant that indexes PDFs into a searchable vector library and exposes MCP tools for semantic search, claim extraction, contradiction detection, and multi-step research synthesis.-
- AlicenseAqualityCmaintenanceEnables an AI assistant to search scientific literature across OpenAlex and Semantic Scholar, download supported Elsevier and Springer Nature full texts, and build a local searchable index so questions can be answered with citations to original paper passages. It runs locally over stdio with CPU-based embeddings and needs no Qdrant account, Docker, GPU, or LLM API key of its own.11MIT
- AlicenseNot gradedqualityBmaintenanceA local-first paper RAG server that enables searching and managing academic PDFs via MCP tools, supporting metadata enrichment and citation graphs.1MIT
- AlicenseAqualityAmaintenanceA local MCP server for searching scientific papers, retrieving metadata and abstracts, and legally downloading Open Access PDFs via OpenAlex, CrossRef, and Unpaywall APIs.53MIT
TDQS
Scored across 16 tools
Most tools target distinct resources or actions: seed CRUD, feedback, workspace setup, and retrieval are clearly separated. The main overlap is between search_local (which includes fulltext) and search_fulltext, plus similar_to may be confused with local search, though descriptions clarify the intended scope.
Tool names consistently use snake_case and are readable, with many following verb_noun patterns like list_seeds, add_seed, get_paper, and search_local. A few names such as new_since, must_read, and similar_to deviate from verb_noun but remain understandable and stylistically consistent.
The 16 tools are just above the typical 3-15 range, but each appears to serve a specific function across workspace setup, seed management, search, retrieval, feedback, and status reporting. The set is slightly heavy but not bloated for a local literature management server.
Core seed CRUD, search, fulltext retrieval, feedback, and corpus status are covered well. However, query management is only partially exposed via list_queries with no add/remove/update tools, and there is no explicit ingestion or PDF parsing trigger, which are notable gaps for the literature workflow.