Tally API MCP Server

Tally API MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Enables AI agents to access and interact with DAO governance data from the Tally API.

What you get

A Model Context Protocol (MCP) server for interacting with the Tally API. This server allows AI agents to fetch information about DAOs, including their governance data, proposals, and metadata.

• List DAOs sorted by popularity or exploration status
• Fetch comprehensive DAO metadata including social links and governance information
• Pagination support for handling large result sets
• Built with TypeScript and GraphQL
• Full test coverage with Bun's test runner

What the assistant can call

Once Tally API is connected, these are the calls the assistant has available:

• list_daos — Parameters: - limit (optional): Maximum number of DAOs to return (default: 20, max: 50) - afterCursor (optional): Cursor for pagination - sortBy

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: TALLY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tally API's toolset — list_daos — is a fair guide to whether it matches your workflow. It is maintained by crazyrabbitLTC; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tally api mcp server does with a few real requests.