Skip to main content
Every pack needs one credential before its first call, and every service issues it somewhere different. This table names the place: the link opens it in a new tab, so this page stays where you left it. Most packs take an API key, which is a minute’s work and needs nothing more — API keys covers what Charter does with one. Google, Slack, GitHub, Notion and Shopify each have a guide, because each wants something registered before it will issue a credential, and Stripe has one for the key worth preferring. Google’s takes ten minutes of console screens, and every guide has a screenshot for each screen, because they are much easier with pictures. Set the variable and the pack reads it on its next call: no configure(), no restart. The order a pack checks them in is on environment fallbacks.

​
Your users’ accounts

Everything above connects one account — yours — to a script, an agent or an MCP server you run. A product where each user connects their own needs more: a consent route inside your app, a grant per user, and somewhere to keep them. The console steps are the same, so do the guide first, then getting the grant and serving many users.
  • Set up Google — the OAuth client every Google pack needs, screen by screen
  • Set up Slack — an app from a prefilled manifest, and its bot token
  • Set up GitHub — a token with the scopes already ticked
  • Set up Notion — an integration, and the pages it may read
  • Set up Stripe — the secret key, and the restricted one to prefer
  • Set up Shopify — a Dev Dashboard app on your store, and its client ID and secret
  • Credentials — every credential provider, as reference