Skip to main content
pdsx ships as a plugin for Claude Code and Codex. Installing it registers the hosted MCP server and a set of skills in one step — the server gives an agent the tools, the skills teach it the parts that are easy to get wrong. Nothing runs locally: the bundled MCP server is hosted.

​
install

​
what you get

Three skills, loaded on demand — installing all of them costs no context until one becomes relevant. Plus the eight MCP tools described in MCP server.

​
MCP tools or the CLI?

The MCP server covers ordinary record CRUD with structured output. The CLI covers everything else.
Permissioned data is CLI only. There are no MCP tools for com.atproto.space.* while the proposal is still experimental.

​
authentication

The skills assume credentials come from the environment for CLI use:
For the MCP server, credentials are passed as headers — see MCP server. Self-hosted accounts need no extra configuration; the PDS is resolved from your handle.

​
using it with protopack

protopack bundles the pdsx MCP server alongside the Microcosm services. Installing both is fine — identical server configs are deduped, so the tools register once, not twice. Verified with both plugins loaded: eight pdsx tools total, one copy of each. The pairing is worth having. protopack’s constellation skill answers “who interacted with this record” through the global backlink index — far better than paginating an account’s posts to find replies, which is what you’d otherwise reach for.