The settings file
Everything you change in the app is saved in one text file, config.toml, in SolutionMCP's settings folder. You
never have to open it, but you can: the app keeps your comments and formatting, and changes you make by hand apply
right away.
Where things are
| On | The settings folder |
|---|---|
| Mac and Linux | ~/.config/solution-mcp |
| Windows | %APPDATA%\solution-mcp |
The Overview page shows the folder, with Open buttons. Inside it:
| File or folder | What it holds |
|---|---|
| config.toml | Your settings. |
| packs | Your own tools. |
| secrets.toml | Your secrets. Only you can read it. |
| data | The activity log, memories, and keys SolutionMCP uses. |
What's in the settings file
The main sections, each optional:
| Section | Settings |
|---|---|
| [toolsets] and [tools] | Which toolsets and tools are on. |
| [policy] | The permission mode, how SolutionMCP asks you, whether commands offer "Allow until restart" (remember_commands), and rules. |
| [files] | The folders the AI can use, and read-only. |
| [shell] | Commands that run without asking, and commands that are always blocked. |
| [web] | Limits for web requests. |
| [audit] | The activity log. |
| [server] | Compact mode and pinned tools. |
| [http] | For apps that connect by URL. |
| [[connect]] | Other MCP servers. |
| [profiles.NAME] | Profiles. |
If something goes wrong
- A mistake in the file shows on the Overview and Health check pages, and the AI apps keep using the last settings that worked.
- Each time the app saves, the previous version is kept as
config.toml.bak. Copy it back to undo. solution-mcp config validatechecks the file and every pack from a terminal.
Tip: Want commands that always run without asking, like
git status? Add them under[shell]asallow = ["git status*"].