AssemblyMCP
Related Servers
Alternatives to AssemblyMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for the Korean National Assembly Open API, enabling querying of bills, members, votes, committees, and more via natural language.20Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables searching and retrieving Korean statutes, precedents, and constitutional court decisions via MCP, using the National Law Information Center API.4,664 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables exploration of Korean National Assembly data by connecting bills, committee reviews, and official records. Allows users to ask natural language questions and receive structured answers with citations to original documents.26Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access real-time legislative data from the Korean National Assembly including members, bills, votes, and schedules through 276 Open APIs. Supports dual transport modes (stdio/HTTP), configurable Lite/Full tool profiles, and in-memory caching for efficient querying.17 npm89MIT
- FlicenseAqualityBmaintenanceEnables AI systems to search, retrieve, and analyze Korean legal information from the National Law Information API (law.go.kr), including laws, administrative rules, English translations, and law-ordinance linkages.262-
- FlicenseAqualityCmaintenanceMCP server that enables AI agents to search Korean laws and retrieve article contents using the Korean Ministry of Legislation's law information API.2-
TDQS
Scored across 26 tools
Several tools have overlapping mandates: bill_timeline duplicates get_bill_history, get_legislative_research_kit overlaps get_assembly_info, and analyze_legislative_issue/issue_brief both produce comprehensive topic reports. Voting and committee tools are mostly distinct, but the duplication makes tool selection ambiguous.
Most tools follow a get_/ search_/ analyze_ verb-noun pattern, but a few noun-first names (bill_timeline, legislative_impact_map, watch_action_plan, issue_brief) and meta tools break the pattern. It is still readable because the prefixes are clear when present.
26 tools is above the comfortable range for an MCP surface, and several could be consolidated (bill history/timeline, issue brief/analysis, the two meta guides). The broad National Assembly domain and raw API backdoor justify some size, but the effective surface feels inflated.
The set covers core legislative workflows: bill search/detail/history, voting results, member info, committee info, meetings, schedules, and reports. The list_api_services/get_api_spec/call_api_raw pipeline plus get_api_code_guide provides an escape hatch for uncovered OpenAPI endpoints, leaving only minor high-level convenience gaps.