An MCP server for Bluesky and the AT Protocol

Give your MCP client public Bluesky and AT Protocol tools without handing it an account password.

By The Bluesky.bot team

Published:
Updated:
Reviewed:

What your client can do

Public tools resolve handles and DIDs, inspect public protocol data, and perform pure computations. No Bluesky app password is accepted by this MCP endpoint. A creator token or MCP OAuth connection can raise public-tool quotas; listing tools have their own explicit permission and cannot claim or release handles.

Public MCP tools
ToolMCP nameHTTP cacheQuota cost
Declared automation checker

See the automation signals an account makes public.

bot_signals60 seconds3 unit(s)
DID finder

Get the DID behind any Bluesky handle.

find_did60 seconds1 unit(s)
Handle finder (DID to handle)

Find the handle behind a DID.

find_handle60 seconds1 unit(s)
Bluesky whois

Everything public about a handle or a DID.

whois_lookup60 seconds3 unit(s)
Account age checker

See when any account joined Bluesky.

check_account_age60 seconds1 unit(s)
AT-URI converter

Turn a bsky.app link into an at:// URI, and back.

convert_at_uri60 seconds1 unit(s)
TID decoder

Read the date hidden in a record key.

decode_tid1 year1 unit(s)
Post character counter

Count your post the way Bluesky does.

count_post_characters1 year1 unit(s)
Rich text facet builder

Mentions, links and hashtags with their byte offsets.

build_post_facetsNot cachedDepends on the request
Custom domain handle checker

Find out why your handle is invalid, and how to fix it.

check_custom_handleNot cached2 unit(s)
Handle availability checker

Is your name free on Bluesky?

check_handle_availabilityNot cached1 unit(s)
PLC history viewer

Every handle change, server move and key change of an account.

plc_history5 minutes2 unit(s)
Starter pack analyser

See who is in a starter pack, with stats and bots.

analyse_starter_pack5 minutesDepends on the request
Post and thread viewer

Read any public Bluesky post or thread, no account needed.

view_bluesky_post60 seconds3 unit(s)
Feed inspector

Preview a custom feed and find out why it shows nothing.

inspect_bluesky_feedNot cached3 unit(s)
Label inspector

See who applied a label and what it means.

inspect_bluesky_labels5 minutesDepends on the request
Follower list export

Back up a public follower or following list as CSV.

preview_bluesky_follows5 minutes2 unit(s)
Repository explorer

Browse an account’s public records on its own data server.

explore_atproto_repo5 minutes2 unit(s)
Other MCP tools
MCP nameToolAuthenticationCapabilities
check_handleCheck whether a Bluesky.bot handle is availablePublicRead only
resolve_handleResolve a claimed Bluesky.bot handlePublicRead only
search_botsSearch the public bot directoryPublicRead only
get_botRead one public bot’s detailsPublicRead only
search_docsSearch the developer documentationPublicRead only
read_docRead a documentation page as MarkdownPublicRead only
list_my_botsList the token owner’s bots (handles permission)Creator token with the required permissionRead only
get_listingRead an owned bot’s listing (listing permission)Creator token with the required permissionRead only
update_listingUpdate only an owned bot’s listing fields (listing permission)Creator token with the required permissionUpdate own listing only

Set it up

Point a Streamable HTTP client at /api/mcp on this site. These are configuration examples, not a claim that every desktop client version was exercised. Public tools work without credentials. See the agent integration reference for protocol and authentication details.

Claude Code
claude mcp add --transport http bluesky-bot https://bluesky.bot/api/mcp
VS Code (.vscode/mcp.json)
{
  "servers": {
    "bluesky-bot": {
      "type": "http",
      "url": "https://bluesky.bot/api/mcp"
    }
  }
}
Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "bluesky-bot": {
      "url": "https://bluesky.bot/api/mcp"
    }
  }
}

For Claude Desktop, add this site’s /api/mcp URL as a remote connector in a version that supports Streamable HTTP. Use its OAuth connection if your client needs it.

Configuration formats vary by client version. Never put a Bluesky app password in these examples. An optional Bluesky.bot token or OAuth connection has separate permissions.

Three recorded protocol sessions

These are real sessions with the MCP JavaScript SDK client, version 1.32.2, against this service. Each initialized a connection, listed tools, called one public tool and closed the connection. The question explains the intent; the result is the tool response. These are protocol tests, not invented conversations with an AI model.

Captured

Input

{
  "question": "Which DID does the official bluesky.bot handle resolve to?",
  "method": "tools/call",
  "params": {
    "name": "find_did",
    "arguments": {
      "handle": "bluesky.bot"
    }
  }
}

Captured output

{
  "client": "MCP JavaScript SDK",
  "clientVersion": "1.32.2",
  "transport": "Streamable HTTP",
  "server": {
    "name": "bluesky-bot",
    "title": "Bluesky.bot",
    "version": "1.1.0"
  },
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"status\":\"found\",\"handle\":\"bluesky.bot\",\"unicodeHandle\":null,\"dns\":{\"status\":\"found\",\"did\":\"did:plc:ulmk4vmvoobkemd3w2tkwhu5\"},\"https\":{\"status\":\"none\"},\"appview\":{\"status\":\"found\",\"did\":\"did:plc:ulmk4vmvoobkemd3w2tkwhu5\"},\"did\":\"did:plc:ulmk4vmvoobkemd3w2tkwhu5\",\"method\":\"dns\",\"verified\":true,\"claimedHandle\":null,\"warnings\":[]}\n\nTool page: https://bluesky.bot/tools/did-finder"
      }
    ],
    "structuredContent": {
      "tool": "did-finder",
      "url": "https://bluesky.bot/tools/did-finder",
      "result": {
        "status": "found",
        "handle": "bluesky.bot",
        "unicodeHandle": null,
        "dns": {
          "status": "found",
          "did": "did:plc:ulmk4vmvoobkemd3w2tkwhu5"
        },
        "https": {
          "status": "none"
        },
        "appview": {
          "status": "found",
          "did": "did:plc:ulmk4vmvoobkemd3w2tkwhu5"
        },
        "did": "did:plc:ulmk4vmvoobkemd3w2tkwhu5",
        "method": "dns",
        "verified": true,
        "claimedHandle": null,
        "warnings": []
      }
    }
  }
}
Captured

Input

{
  "question": "Does this short sample fit a Bluesky post?",
  "method": "tools/call",
  "params": {
    "name": "count_post_characters",
    "arguments": {
      "text": "Hello Bluesky! 👋"
    }
  }
}

Captured output

{
  "client": "MCP JavaScript SDK",
  "clientVersion": "1.32.2",
  "transport": "Streamable HTTP",
  "server": {
    "name": "bluesky-bot",
    "title": "Bluesky.bot",
    "version": "1.1.0"
  },
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"graphemes\":16,\"bytes\":19,\"graphemesLeft\":284,\"bytesLeft\":2981,\"over\":false,\"limits\":{\"graphemes\":300,\"bytes\":3000},\"parts\":[]}\n\nTool page: https://bluesky.bot/tools/character-counter"
      }
    ],
    "structuredContent": {
      "tool": "character-counter",
      "url": "https://bluesky.bot/tools/character-counter",
      "result": {
        "graphemes": 16,
        "bytes": 19,
        "graphemesLeft": 284,
        "bytesLeft": 2981,
        "over": false,
        "limits": {
          "graphemes": 300,
          "bytes": 3000
        },
        "parts": []
      }
    }
  }
}
Captured

Input

{
  "question": "What timestamp does this example record key encode?",
  "method": "tools/call",
  "params": {
    "name": "decode_tid",
    "arguments": {
      "tid": "3l6oveex3ii2l"
    }
  }
}

Captured output

{
  "client": "MCP JavaScript SDK",
  "clientVersion": "1.32.2",
  "transport": "Streamable HTTP",
  "server": {
    "name": "bluesky-bot",
    "title": "Bluesky.bot",
    "version": "1.1.0"
  },
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"tid\":\"3l6oveex3ii2l\",\"timestamp\":\"2024-10-17T07:06:51.642Z\",\"microseconds\":\"1729148811642318\",\"clockId\":17,\"topBitSet\":false}\n\nTool page: https://bluesky.bot/tools/tid-decoder"
      }
    ],
    "structuredContent": {
      "tool": "tid-decoder",
      "url": "https://bluesky.bot/tools/tid-decoder",
      "result": {
        "tid": "3l6oveex3ii2l",
        "timestamp": "2024-10-17T07:06:51.642Z",
        "microseconds": "1729148811642318",
        "clockId": 17,
        "topBitSet": false
      }
    }
  }
}

Choose a server for the job

Our public tools are useful for checking identity and protocol details without account credentials. If your agent needs to post, a server with explicit write permissions may fit better. Treat an app password as a secret, review the granted tools and retain human confirmation for consequential changes. Read-only annotations describe tools; they do not make untrusted text instructions safe.

The following facts were checked in each linked README on 15 November 2026. We did not run these other servers or audit their security. Their features and deployment requirements may change.

ServerTransportAuthenticationCapabilitiesLicenceLatest commitUseful forREADME checked
brianellin/bsky-mcp-serverLocal stdioBluesky app passwordReads and writesMITAn account’s timeline and posting
Ravishka17/Bluesky-MCPStreamable HTTPPublic reads; app password headers for writesReads and writesUnlicenseA self-hosted HTTP client with write tools
cameronrye/atproto-mcpstdio; optional HTTPPublic reads; account credentials for private data/writesReads and writesMITA broader AT Protocol account toolkit

Limits and fair use

Anonymous: 60 quota units per 60 seconds and 2000 per 24 hours. A valid creator token raises both limits by 10 times when its owner has at least one active bot.

A call consumes its tool’s weight in both quotas. Server lookups also share an upstream budget; complex checks can be refused before your own quota runs out.

MCP separately allows 120 requests per 60 seconds for anonymous clients; eligible creator tokens raise that limit too. Discovery and tool-list requests count here even when no tool is called.

MCP tool failures return isError: true in the tool result. Transport guards may instead return an HTTP error; rate-limit refusals include Retry-After. Use the protocol reference for the exact JSON-RPC errors.

We count the tool and channel, not your input. Tool-input query strings are excluded from access logs. Do not send secrets, private posts or another person’s credentials.

The service is free and best effort, without an uptime SLA. Reuse cacheable results, respect retry delays and contact us for a different use case.

An HTTP alternative

If you do not need MCP, use the free tools API. The same tool definitions supply its schemas and answers. No MCP directory registration, uptime guarantee, independent security audit or third-party deployment test is implied by this page.

Prefer a terminal? Compare the Bluesky command-line clients, including the published bsbot version and its current limits.

Questions

Does it need my Bluesky password?

No. Public tools need no account password or token. Optional Bluesky.bot tokens and OAuth connections have separate permissions.

Can it publish, follow or delete posts?

Public tools cannot. Listing tools may update only a creator’s own directory information with explicit permission; they cannot manage Bluesky handles.

Which transport does it use?

Streamable HTTP at /api/mcp. Use a compatible client; configuration syntax varies by version.

Is there an HTTP API instead?

Yes. The tools API at /api/v1/tools exposes the same public tool definitions.

Sources