Secrets
Some tools need an API key, a token or a password, for example to use a weather service or your GitHub account. Keep those in Secrets, not inside your tools: SolutionMCP stores them safely and fills them in when a tool runs.
On Free, your tools use 1 secret. If you have more, click Use in Free next to the one to use; the others are kept for when you have a license.
Add a secret
- Open the Secrets page.
- Under Add or change a secret, type a name, like
GITHUB_TOKEN, and the value. - Click Save.
Saving a name that already exists replaces its value. Values are never shown again, not even to you: to change one, save it again.
What the page shows
- Missing secrets: secrets your tools use that aren't set yet. Add them, and those tools start working.
- Saved secrets: the names you've saved, and which tools use each one. Remove deletes a secret; tools that use it stop working until you add it again.
How they're protected
- They're kept in a separate file only your account can read.
- The AI never sees them, and SolutionMCP's file tools can't read the file.
- They're hidden as
***in approval questions and on the Activity page.
To use a secret in a tool you make, see Secrets in your tools.