io.github.lacausecrypto/poetrydb
Related Servers
Alternatives to io.github.lacausecrypto/poetrydb
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables searching and retrieving poems from the PoetryDB API by title, keyword, or author, and also provides random poems for inspiration.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to explore a public-domain poetry collection by searching poems by title, finding poems whose lines contain a given phrase, pulling one or more random poems, and listing available authors. It returns full poem text with author and line-count details, and works either through a hosted gateway or as a local stdio server without an account.96 npmMIT

Ganjoor MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants and agents to browse Persian classical poetry collections, read poems and verses, run prosody and rhyme analysis, trace reply-poems, look up recitations and commentary, and explore related-people and family-tree data through structured read-only tools.4474 npm8MIT- AlicenseBqualityDmaintenanceExposes 97 official Shanghai Library open data APIs and the Sou-Yun poetry database (1.99 million poems) as 12 MCP tools, covering genealogy, ancient books, calligraphy, historical buildings, and more. Enables MCP clients to query these datasets using natural language.124MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to search Chinese poems by title, content, author, dynasty, or category; check recitations and dictation; generate appreciation text; create TTS recitations with subtitles; and produce calligraphy practice sheets.MIT
- AlicenseAqualityBmaintenanceEnables search and retrieval of Shakespeare monologue metadata including character, play, first line, and paraphrases through various tools.9289 npmMIT
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes, but get_sonnets and get_haikus overlap with search_by_linecount since 14-line and 3-line poems are special cases. An agent might be unsure whether to use the specialized get_* tools or the more general search_by_linecount.
Tool naming mixes several patterns: catalog_* (catalog_overview, catalog_category), search_by_* (search_by_author, search_by_title, etc.), list_* (list_authors, list_titles), get_* (get_sonnets, get_haikus), and random_poem (no prefix). This inconsistency can make tool selection less predictable.
With 12 tools, the count is well within the expected range for a domain-specific server. Each tool serves a distinct function and none feels superfluous or excessive for a poetry database.
The toolset covers searching, listing, and random access, along with helpful meta-tools for discovery. Minor gaps include the lack of a direct 'get poem by ID' or 'get full poem content' endpoint, which forces reliance on search results. Overall, the surface is reasonably complete for common poetry browsing workflows.