Categories › AI & Agents › Multi-agent, orchestration & workflows
Public FY2027 NDAA tracker: bill status, section text, House vs Senate diffs, and news from ndaa.ai
Remote server: your requests and data go to mcp.ndaa.ai. Claude Code: claude mcp add --transport http ndaa-ai-fy2027-tracker https://mcp.ndaa.ai/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
get_status — Current FY2027 NDAA bill status (H.R. 8800 / S. 4784): headline, summary, next steps, stage tracker, and as-of date. Cite the returned ndaa.search_sections — Search FY2027 NDAA sections by keyword or topic (pay raise, FOCI, OTA, shipbuilding, etc.). Returns matching sections with snippets and canoget_section — Get one FY2027 NDAA section: plain-language summary, statutory text, House and Senate variants when both exist, and the ndaa.ai URL to cite.compare_house_senate — Compare House (H.R. 8800) vs Senate (S. 4784) text for a section number or a topic. Returns which chamber has the section, whether the text latest_news — Latest NDAA news items tracked on ndaa.ai (outlet, date, summary, source URL, and the /news page to cite).list_updates — List ndaa.ai's dated NDAA update posts, newest first: date, title, story count, status note, and the /updates/YYYY-MM-DD URL to cite.get_update — Get one dated NDAA update post (the newest if no date): intro, every story (headline, outlet, summary, source URL), status note, and the canlist_guides — List NDAA.AI explainer guides (status, House vs Senate, FY2027 vs FY2026, military pay raise) with canonical URLs.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.