The cicada.guide plugin connects Claude to U.S. state legislative data: bills, bill text, legislators, sessions, roll calls, and individual votes. Ask in plain language and get answers built from the record.
At the Claude Code prompt, run these two commands one at a time. Claude Code runs a command only when it starts the message, so pasting both at once runs just the first.
The quickstart walks through the rest.
/plugin marketplace add cicada-guide/plugin
/plugin install cicada-guide@cicada-guide
The install command asks where to install the plugin: choose Install for you to use it in every project.
When the summary says Plugin is now active, you're set. If the plugin is left pending instead, run /reload-plugins. Then run /mcp and check that guide-public shows as connected.
cicada-guide/plugin.In chat, the skill and the three commands work. The two subagents run only in Cowork and Claude Code. A plugin added here is saved to your Claude account, so it's also available in Cowork and Claude Code.
Connect the server directly at https://public.cicada.guide/mcp-anthropic. You get the raw tools without the plugin's guidance. See Using another MCP host.
Three slash commands run the longer workflows. With no argument, each one asks which bill or legislator you mean, and in which state.
A sourced brief on one bill: status, sponsors, text, roll calls, and votes. Give it a topic and it lists matching bills first.
One legislator's voting history or vote on one bill, or a party breakdown of one roll call.
One legislator's recorded seat and the contact details on record, on a contact card.
The get-legislation skill loads by itself on any state-legislation question. Two subagents handle the heavy lifting: one assembles full bill briefs, the other pins an ambiguous name to one legislator.
In hosts that render MCP Apps, answers end with a bill card, a legislator record, or a contact card. Hosts that can't render cards get a text version, and the written answer stands on its own.
No federal congressional bills, municipal ordinances, or ballot measures.
The tools retrieve legislative records. They can't send messages, contact officials, file documents, or change anything.
The plugin doesn't score, rank, or predict legislators.
Roll-call tallies aren't results, and an enrolled document alone doesn't confirm enactment.
No tool maps an address or district to a legislator, so “my senator” gets a question back asking for a name and state.
When an email, phone number, or seat isn't on record, the answer says so.
Install, confirm the connection, and ask your first questions.
What each command, skill, and subagent does, and the cards they end with.
The server's tools, the data model, and the limits to know.
Connection problems, missing commands, rate limits, and errors.
What the plugin sends, what the server records, and where the data comes from.
Plugin source, changelog, and issues.
Legislative records are sourced from LegiScan and Open States, and a bill's status may have advanced since the last data load. Treat answers as research support, not as an authoritative legal record.
