







atpxrpc is a tool in the atproto-crates that makes it easy to invoke XRPC methods. It supports multiple identities, direct and proxy XRPC calls, binary inputs, and more. Install with homebrew: brew tap ngerakines/tap && brew install atpxrpc Read more at ngerakines.me/atpxrpc.html
atpxrpc
ngerakines.meMar 9, 2026 at 2:17 PM
Authenticated XRPC Calls in Lexicon Garden - Nick's Blog
ATProtocol OAuth pairs effortlessly with Lexicon Garden to make it easy for developers to experiment with authenticated XRPC endpoints.
ngerakines/atproto-tools - Docker Image
A comprehensive collection of Rust components for creating AT Protocol applications. This workspace provides essential building blocks for identity management, record operations, OAuth 2.0 authentication flows, HTTP client operations, XRPC services, and real-time event streaming.
ATProto in Practice #1: Identity
I’m starting a new blog post series that I’ve named “ATProto in Practice”. I want to go through some practical tasks that you’re likely to need when working with the protocol, using Ruby and my Ruby gems for the examples. These will (hopefully) be a bit shorter than my standard book-length blog posts here 🫠

/atproto-identity-rs/crates at main · smokesignal.events/atproto-identity-rs
A library for ATProtocol identities.
millipds/src/millipds/repo_ops.py at main · DavidBuchanan314/millipds
A from-scratch atproto PDS implementation in Python - DavidBuchanan314/millipds
atpmcp is a local MCP server that is part of the atproto-crates project. It supports the same authentication as the atpxrpc tool and is using the latest MCP features. Install with homebrew: brew tap ngerakines/tap && brew install atpmcp Read more at ngerakines.me/atpmcp.html
atpmcp
ngerakines.meMac or Linux user with homebrew? Check out atpcid: 1. brew install ngerakines/tap/atpcid 2. echo '{"text": "hello world"}' | atpcid -- Seems simple right? There's more, but first big thanks to @knowtheory.net and @filippo.abyssdomain.expert for working through some fun ATProtocol workflows.
XRPC requests between atproto servers are authenticated using JWTs. There are some inconsistencies in how OAuth permissions, PDS proxy headers, and JWTs all represent the "audience" of these tokens. This proposal gives background and describes a rough solution. Looking for rapid feedback!
proposals/0013-service-auth-refs at main · bluesky-social/proposals
github.comatproto devs, read this:
Things we shouldn't say in polite company - Sherif's blog
sherif.pckt.blogWe just shipped our entire API as XRPC endpoints 🎉 Don't like our directory? Index the firehose yourself Hate our client? Build your own Want your AI to register new machine for you to earn? Automate it Need to add inference to your atproto app? Easy peazy See the full api here 👇
AppView API · co/core
console.cocore.dev
atmoBB Forums

atmeet — Blueskyで、集まろう。

GainForest — Biodiversity Observations & Nature Projects
badge.blue — CID-First Attestation Specification
arecipe

Radial