← lunenburgbudgetproject.org

INDIVIDUAL MCP TOOL

read_first

The grain of every table and the specific ways to get a confident wrong answer out of this data.

lunenburgbudgetproject.orgnone authenticationAvailability not checked

LIVE ENDPOINT

https://lunenburgbudgetproject.org/mcp

No auth detected

Connect to this endpoint to inspect the live schema for read_first and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

lunenburgbudgetproject.org

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.lunenburg-budget]
url = "https://lunenburgbudgetproject.org/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "lunenburg-budget": {
      "type": "http",
      "url": "https://lunenburgbudgetproject.org/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: lunenburg-budget
Remote MCP URL: https://lunenburgbudgetproject.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "lunenburg-budget": {
      "url": "https://lunenburgbudgetproject.org/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "lunenburg-budget": {
      "type": "http",
      "url": "https://lunenburgbudgetproject.org/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "lunenburg-budget",
  "transport": "streamable-http",
  "url": "https://lunenburgbudgetproject.org/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • list_datasets — Every dataset in the archive, with THE YEARS EACH COVERS, its row count and its size.
  • worked_examples — 107 questions this archive can answer, each with the SQL that answers it.
  • search_meetings — Which of the 1,422 published town meeting documents contain a word — every board, 2025 onward.
  • budget_history — What a school budget line was in each year, AT ONE STAGE.
  • staff — How many people the town PRINTED on a school staff roster, by year, school and kind of job.
  • document — Where a document came from: the publisher's URL, our copy, and its sha256 so a reader can check they have the same bytes.
  • query — Any question the other tools do not cover, as one read-only SQL statement over the archive database.