Skip to content
Taproot MCP logo

Taproot MCP

Gives an AI assistant read access to public AT Protocol accounts, records, conversations and lexicons via an MCP server.
Taproot MCP: data, price, alternatives
At a glancechecked Oct 22, 2026

not read yet

Use

For
People connecting an AI assistant to look up public AT Protocol and Bluesky data
How it runs
API
Used for
  • Look up public accounts across the AT Protocol network
  • Browse public records and conversations from network apps
  • Inspect lexicon schemas that network apps use
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 24, 2026
  • MCP servercom.atproto-mcp/taprootverified in the MCP registry
  • Stateanswers, 27 toolschecked 2026-10-24
  • Address to connectmcp.atproto.at/mcp

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Taproot MCP with

Pick up to two.

All 10 alternatives to Taproot MCP →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Taproot MCP for?

Sign in to leave a note
Questions this page answers
  • What is Taproot MCP?

    Gives an AI assistant read access to public AT Protocol accounts, records, conversations and lexicons via an MCP server. It is listed in the Atlas under Developer tools.

  • Who is Taproot MCP for?

    People connecting an AI assistant to look up public AT Protocol and Bluesky data

  • Do people use Taproot MCP?

    Little sign of use.

  • What are alternatives to Taproot MCP?

    In Developer tools, by use: Workato, Desktop Commander MCP, CtrlOps, Unified, Ontonym.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk