MCP server — Things worth knowing before you rely on it

A key is the whole credential. Anyone holding it reads the workspace as that member, and assistant config files store it in plain text on the machine — so a synced or shared config shares the key, and a write-enabled key in a shared config is an editor's pen in everyone's hands. Name each connection after the tool and the laptop it lives on, because that name is how you know which one to revoke. Signing in avoids this: an OAuth connection puts no secret in a file. Revocation is not quite instant. A revoked key can keep answering for up to a minute or so on other servers, while the auth caches expire. A disconnected sign-in stops within fifteen minutes, once its current access token runs out. A CSV export hands back a short-lived link that only opens in a browser already signed in as the acts-as person, and re-checks their permissions at click time. Relative dates resolve in the workspace's timezone, not the agent's.