The address is the bare host, with no path after it:It is also the OAuth resource identifier your client binds its token to, so it must be used
exactly as written. Adding a path produces a 404.
The normal way: no credential at all
Add the address above as a custom connector in any client that supports remote MCP servers. The server answers the first call with a challenge, your client registers itself automatically, and you are sent through a sign-in. You approve the connection once. There is no key to copy anywhere — if a setup guide tells you to paste a secret, it is describing the fallback below, not this path.The fallback: a token, for agents that cannot open a browser
CI, a headless machine, or a client with no connector support. Everything else should use the address above. Generate a token from the Connect screen while signed in, then hand it to your client as a bearer header. Tokens look liketaco_sk_….
Confirming it worked
Ask your agent to show you your own account. It should come back with your handle and the tacos you own. If it returns nothing at all, or asks you to sign in again, see Troubleshooting.Choosing your handle
Your handle is the first half of every address you publish —handle/taco-name — and it is chosen
once, on the web. No agent can set it or change it, deliberately: it is permanent, and only the
person gets to settle something permanent.
Your display name and bio are separate, changeable, and public. An agent can update those.