Japan Parliament Search MCP
Related Servers
Alternatives to Japan Parliament Search MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables full-text search of Japanese National Diet proceedings from 1947 onward, with filters by speaker, party, chamber, and date, plus retrieval of complete speech texts and meeting records.244 npmMIT
- FlicenseAqualityDmaintenanceProvides a structured interface to the Japanese National Diet Library's parliamentary proceedings API, allowing AI models to search and retrieve Diet meeting records and speeches.31-
- FlicenseAqualityBmaintenanceEnables search, retrieval, and summarization of Japanese National Diet meeting minutes via MCP tools.81-
- FlicenseBqualityDmaintenanceMCP server that provides tools and prompts for searching Japanese Diet (国会) proceedings using the National Diet Library API. Enables querying meetings and speeches with various filters and obtaining direct URLs to the records.338-
- AlicenseAqualityAmaintenanceSearches and retrieves Japanese national legislation from the official e-Gov API, providing verifiable citations with stable URLs and human-readable references.651 PyPIApache 2.0
- AlicenseAqualityDmaintenanceFull-text search across all ~10,000 current Japanese laws and regulations (official e-Gov data): keyword search, table of contents, and exact article text.3MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: search_meetings focuses on meeting-level search to understand which committee discussed what, while search_speeches provides full-text speech search. There is no overlap in functionality.
Both tools follow a consistent 'verb_noun' pattern with 'search_' prefix plus a plural noun (meetings, speeches), making the naming predictable and clear.
Only 2 tools is slightly below the typical 3-15 range, but for a focused task like searching Japanese parliament records, this minimal set can be sufficient if it covers the core use cases of meeting discovery and speech retrieval.
The tools cover primary search needs but lack additional capabilities like retrieving individual meeting details, filtering by exact dates, or exporting results. Minor gaps that agents can work around with careful queries.