yay, paru, RPC, gRPC, and MCP

Pass URLs on the command line. Do not pass --save. Quote the RPC URL in zsh because ? is a glob.

yay and paru

yay --aururl https://packages.taur.weirdbrains.com --aurrpcurl 'https://packages.taur.weirdbrains.com/rpc?' -Ss hello
yay --aururl https://packages.taur.weirdbrains.com --aurrpcurl 'https://packages.taur.weirdbrains.com/rpc?' -Sii hello-taur
yay --aururl https://packages.taur.weirdbrains.com --aurrpcurl 'https://packages.taur.weirdbrains.com/rpc?' -G hello-taur

paru --aururl https://packages.taur.weirdbrains.com --aurrpcurl 'https://packages.taur.weirdbrains.com/rpc?' -Ss hello

yay GETs /rpc?. paru POSTs a form to /rpc. -G clones. It does not build. Give each helper a private HOME and XDG_CONFIG_HOME when you are testing.

RPC

curl 'https://packages.taur.weirdbrains.com/rpc/v5/search/hello?by=name'
curl 'https://packages.taur.weirdbrains.com/rpc?v=5&type=info&arg[]=hello-taur'

Dumps: /packages.gz, /pkgbase.gz, /packages-meta-v1.json.gz, /packages-meta-ext-v1.json.gz.

gRPC

taur serve --grpc-bind 127.0.0.1:50051

The package service is https://packages.taur.weirdbrains.com. gRPC stays on the address you set with --grpc-bind (plaintext HTTP/2); it is not served from the project site. Send authorization: Bearer <token>.

MCP

HTTP: POST /mcp on the same server. Stdio: taurctl mcp with TAUR_SERVER or --server pointing at the HTTP API. Public tools search and show packages. Management tools need the bearer token in the MCP client configuration, the same token taurctl login stores.

taurctl --server https://packages.taur.weirdbrains.com login alice
taurctl mcp