Skip to content
Georgia Commons
Menu

For anyone who uses an AI assistant

Bring Georgia's laws, bills, court opinions, and legislative meetings into Claude and ChatGPT

A connector lets your assistant read the documents on this site directly and cite the page it read. Add one address once, then ask your questions in the app you already use.

Machine-readable https://georgiacommons.org/mcp.md · https://georgiacommons.org/index.md · MCP https://mcp.georgiacommons.org/mcp

What it is

A connector, usually called an MCP server (Model Context Protocol), is a small bridge between an AI assistant and a real source of information. Georgia Commons runs one. Once it is connected, an assistant that is asked about a Georgia statute, a bill, or a Supreme Court decision looks the document up and answers from its actual text, with a link to the page it read.

One address covers the Code and the two constitutions, bills, opinions, and House and Senate meetings. It is read-only, it needs no account, and there is nothing to pay for on this end.

How to connect it

In every app the step is the same: paste this address.

Connector URL

https://mcp.georgiacommons.org/mcp

There is no sign-in, no password, and no key. Menu names in these apps change fairly often, so treat the steps below as the shape of the thing rather than the exact words on your screen.

Claude

Add it once and it follows you to every Claude app

  1. Open Settings, then Connectors.
  2. Choose Add custom connector.
  3. Give it a Name. "Georgia Commons" works.
  4. Paste the address above into Remote MCP server URL. Leave the advanced and OAuth fields alone.
  5. Click Add. In a chat, open the tools menu and switch it on.

This works on the Claude web app, the desktop app, and the phone app, and a connector added in one shows up in the others. Every plan including Free can add at least one custom connector. On a Team or Enterprise plan an owner adds it once under organization settings and everyone else turns it on.

ChatGPT

Add it from the website, not the phone app

  1. Open ChatGPT on the web. The phone and desktop apps do not offer this yet.
  2. Go to Settings, then Apps, and choose Create app.
  3. Enter a Name. "Georgia Commons" works.
  4. Leave Connection on Server URL and paste the address above.
  5. Set Authentication to No Auth, confirm, then click Connect.

Deep research and the Responses API reach the same server through its search and fetch tools, so anything connected this way can cite the page it read.

Claude Code and other terminal agents

One command

claude mcp add --transport http georgiacommons https://mcp.georgiacommons.org/mcp

Any client that speaks the streamable HTTP transport can point at the same address. There is nothing else to configure.

OpenAI Responses API

From your own code

from openai import OpenAI

client = OpenAI()
response = client.responses.create(
    model="gpt-5",
    tools=[{"type": "mcp", "server_label": "georgiacommons",
            "server_url": "https://mcp.georgiacommons.org/mcp", "require_approval": "never"}],
    input="What does Georgia law require a landlord to do with a security deposit? Quote it and cite it.",
)
print(response.output_text)

What to ask once it is connected

  • "What does Georgia law require a landlord to do with a security deposit? Quote the statute."
  • "What does House Bill 136 of the 2025-2026 session actually do, and where does it stand?"
  • "Summarize the Supreme Court of Georgia's opinion in docket S26A0060 and quote the holding."
  • "Which chapter of the Georgia Code covers landlord and tenant law? List its sections."
  • "Is this sentence really in O.C.G.A. 44-7-34?" and then paste the sentence.

One tip: Search matches the words of the document. Ask in the words the document would use, not the words of the question. A statute about a child says "minor"; an opinion about a car crash says "motor vehicle". If the first search comes back thin, ask again in the document's words.

What the connector gives your assistant

  • The document itself. Each tool returns the stored source text of a document, so your assistant can read it and quote it.
  • Quotes can be checked. The connector has a tool that reports whether a quotation appears word for word in the stored text. You can ask your assistant to check its quotes with it.
  • The Code carries no interpretation. The statutes and both constitutions are source text only. Georgia Commons does not summarize, explain, or interpret them anywhere, including here.
  • It links to the original. Every answer can name the page it read, and every page links to the official document the state, the General Assembly, or the court published.
  • It reports what it covers. A coverage tool reads what is loaded at the moment it is called, so the answer to "what does this cover?" comes from the stores, not from memory.

Good to know

  • It only reads. Every tool is read-only, and the connector changes nothing. Georgia Commons never receives your conversation with your assistant, only the tool calls it makes. For each call it keeps a count: the tool's name, the time, and what kind of assistant called it, never what was asked. The privacy policy has the details.
  • No account, no key. The documents are public, so the connector is too. It has a generous per-address limit on requests a minute and an hour; past it, the reply says how long to wait.
  • Not a government service. Georgia Commons is an independent project of Georgia Civic Data. It is not affiliated with, operated by, or endorsed by the State of Georgia, its courts, or any agency.
  • Not legal advice. It hands your assistant the text of the law. Reading a statute is not the same as knowing how it applies to you.
  • Assistants still make mistakes. A connector lets the assistant read what a document says; it does not remove the risk that an answer misreads or overstates it. Follow the link for anything that matters.

What the connector can do

The server offers 28 tools. You never call them yourself; your assistant picks the one it needs. They are listed here so you can see exactly what the connector is allowed to do before you add it.

Across the whole site

Five tools that work over every collection at once. The first two give an overview of what is here and what is loaded.

  • `describe_site` Describe Georgia Commons. What Georgia Commons holds, which collections this server has loaded, how identifiers are written, and which tool to call next.
  • `get_coverage` Get collection coverage. Exactly what is loaded right now, read from the stores at the moment of the call: coverage sentences, corpus versions, counts, sessions, years, and licenses.
  • `search` Search all Georgia Commons documents. Search every collection, or one, and get back a short list of matches with a title and a link, in the shape ChatGPT connectors and deep research call.
  • `fetch` Fetch a document by id. Read one document by its identifier and get the same text the site serves, with the page address to cite. A long document comes a part at a time.
  • `verify_quote` Verify a quotation. Check whether a quotation appears word for word in the stored text. Deterministic, with no model involved.

The Code and the two constitutions

The Official Code of Georgia Annotated and the Georgia and United States constitutions, as source text. No summary, no interpretation, no model anywhere in this path.

  • `code_describe_structure` Describe the Official Code of Georgia Annotated. How the Code is organized and how citations are written, plus the list of titles. A short overview for statute questions.
  • `code_lookup_section` Look up a Georgia Code section. One section by its citation, written any of the ways people write it.
  • `code_lookup_sections` Look up several Georgia Code sections. Several sections at once, as a list or a range such as 44-7-30 through 44-7-35.
  • `code_browse` Browse the Georgia Code's titles and chapters. Walk the hierarchy: the titles, a title's chapters, or a chapter's sections.
  • `code_get_chapter` Read a Georgia Code chapter. Every section of one chapter with its text, a window at a time.
  • `code_search` Search the Georgia Code or a constitution. Full-text search of the Code. A citation among the words returns that section first, and an act's short title returns the section that states it.
  • `code_find_chapter` Find Georgia Code chapters by topic. For when the topic is known but the citation is not: the titles and chapters whose headings carry the words.
  • `code_find_act` Find a Georgia Code section by an act's name. Laws by the short title the statute itself states, such as Joshua's Law.
  • `constitution_lookup` Look up a Georgia or U.S. constitution provision. One provision of the Georgia or United States constitution as printed in the Code.
  • `constitution_browse` Browse the Georgia or U.S. constitution. The articles and sections of either constitution, one line each.

General Assembly bills

Bills of the Georgia General Assembly: the full text as filed, and the plain-language summaries Georgia Commons wrote, always labeled and always after the text.

  • `bills_lookup` Look up a Georgia General Assembly bill. One bill by its number, written any of the ways people write it.
  • `bills_get_text` Read a bill's text. The stored bill text alone, a window at a time.
  • `bills_list` List the bills of a session. The bills of a session in number order, filtered by chamber, kind, status, or subject.
  • `bills_search` Search Georgia General Assembly bills. Full-text search over bill text, titles, and labeled summaries.

Supreme Court of Georgia opinions

Opinions of the Supreme Court of Georgia, with the same rule: the court's text first, anything Georgia Commons wrote after it and labeled.

  • `opinions_lookup` Look up a Supreme Court of Georgia opinion. One opinion by its docket number, reporter citation, record id, or case name.
  • `opinions_get_text` Read an opinion's text. The stored opinion text alone, a window at a time.
  • `opinions_list` List Supreme Court of Georgia opinions by year. The opinions filed in a year, in filing order, filtered by case type.
  • `opinions_search` Search Supreme Court of Georgia opinions. Full-text search over opinion text, case names, and labeled summaries.

House and Senate meetings

Machine transcripts of Georgia House and Senate floor sessions, standing committee meetings, and Rules Committee meetings, with the summaries Georgia Commons wrote, always labeled. A transcript is not an official record and names no speaker; every timestamp links to the moment in the General Assembly's video.

  • `meetings_lookup` Look up a House or Senate meeting. One meeting by its address, the General Assembly's video, or a body and a date, such as House Rules 2/5/2026.
  • `meetings_get_transcript` Read a meeting's transcript. A meeting's transcript alone, each turn with its timestamp, a window at a time.
  • `meetings_list` List House and Senate meetings. The published meetings of a day, a year, or a body, or the newest first.
  • `meetings_search` Search House and Senate meetings. Full-text search over the transcripts and the labeled summaries, with the moments that match. A bill number lists the meetings that took the bill up.
  • `meetings_for_bill` Find the meetings that took up a bill. The meetings that took up a bill, each with its moment in the video and the summary of the discussion.

If your assistant cannot add a connector

Every document page here has a small row of buttons under its title that does much the same job one page at a time.

  • Copy for LLM. Puts the page's full source text on your clipboard, ready to paste into any assistant.
  • Send to AI. Opens Claude or ChatGPT with the page's address already in the prompt, so it can fetch the document on its first turn.
  • View as markdown. Every page has a plain Markdown version at its address plus .md, and the source text alone at its address plus /text.

Building something rather than chatting? The JSON API needs no key either, and https://georgiacommons.org/for-assistants is the one-screen reference for an agent's operator: the URL grammar, one worked example per collection, and every address written out in full.