PlugsightDocs

Keep app passwords and API keys safe

Where app passwords, API keys and server links belong, habits that keep them safe, and exactly what to do if one leaks.

Plugsight uses three kinds of secret. Each one gives access to something different, so each needs its own care.

Secret What it is What someone with it could do
App password A password you create at your email provider (Gmail, iCloud, Yahoo, AOL, Zoho and others) for Plugsight to use. Sign in to that mailbox by itself, outside Plugsight.
API key (starts mcpk_) The key for one MCP server, for Claude Code, scripts or the developer API. Use everything that MCP server reaches, and make changes if the server and accounts allow them.
Your Plugsight sign-in Your password, sign-in link or Google or Microsoft login. Everything in your Plugsight account.

A Server URL on its own isn't enough to get in: an AI app that uses it must sign in to your Plugsight account and click Allow access. There's still no reason to share it.

App passwords

  • Make an app password only for Plugsight, and name it so you'll recognise it later, for example "Plugsight". Don't reuse it anywhere else.
  • Paste it straight into Plugsight, then close the provider's page. Some providers, including Google, show it only once; you don't need to keep a copy. If you ever need to reconnect, make a new one.
  • Never paste it into an AI chat, an email or a shared document.
  • Delete it at your provider when you remove that mailbox from Plugsight. Your normal password isn't affected.

Plugsight encrypts app passwords with AES-256-GCM before saving them, decrypts them only on its own servers when a request needs them, and never sends them to your AI app. See How credentials are stored.

Problems creating one: App password problems.

API keys

  • Most AI apps don't need a key. Claude, ChatGPT and most others sign in through a window. Create a key only for tools that can't, such as Claude Code on a server, scripts or the developer API.
  • One server per key holder. Each server has at most one key. Give each script or system its own server with Selected accounts, so each key reaches the least it can.
  • Untick Allow changes on servers whose key only needs to read. Then the key can't send or change anything.
  • Keep keys on servers, in environment variables or your platform's secret settings. Never put one in web page code, a mobile app, a public repository or a chat.
  • Don't share a key with a teammate so they can use your accounts. Everything done with it happens on your account. Each person should have their own Plugsight account. See Onboard a teammate.
  • Revoke keys you no longer use: on the server's page, API key → Revoke key.

Plugsight shows a key once and stores only a hash of it, so nobody, including Plugsight, can show it to you again. If you lose it, regenerate it. See API keys.

Your Plugsight sign-in

  • Use a password of at least 10 characters that you don't use anywhere else, or sign in with Google or Microsoft.
  • Don't share your login. Plugsight has no shared or team accounts.
  • Check Activity, filtered to Sign-ins, now and then for sign-ins you don't recognise.

See Change or reset your password.

If a secret leaks

Act in this order. Each step takes effect straight away.

  1. Stop changes. On Permissions, click Pause everything. Your AI can still read, but nothing can be sent or changed.
  2. Close the leaked door:
    • API key: on the server's page, Regenerate key → Replace key (or Revoke key). The old key stops working at once. Then update the places that use it.
    • App password: delete it at your email provider. Then make a new one and reconnect the mailbox on Connections.
    • Plugsight sign-in: change your password. Then, on each MCP server, use Disconnect all AI apps, and reconnect your own apps.
  3. Check what happened. On Activity, filter to AI apps and look for anything you didn't do. Calls made with an API key show as "Developer API" or the app's name, with "via [server name]".
  4. Resume. Once you're sure, click Resume all on Permissions.
  5. Tell us if you think someone got into your account: email info@plugsight.app. See Security issues and the privacy policy.