Tools and packs explained
A tool is one thing the AI can do, like "read a file" or "check the weather". Each tool has:
- a name the AI uses to call it, like
weather - a description that tells the AI what it does and when it helps
- parameters: what the AI fills in, like the city
- what it runs: a program, a script, a web request, or other tools in a row
- how much it can change: only looks, makes changes, or can delete or overwrite
A pack is a file that holds tools. Packs keep related tools together, and each pack shows up on the Tools page
as a toolset with its own switch. Your packs live in the packs folder inside SolutionMCP's settings folder. The
Overview page has a button that opens it.
SolutionMCP's own system tools come in packs too: macos, windows, wsl, linux and dev.
Three ways to make tools
- The tool editor in the app: a form, no file editing. Start with Your first tool.
- Ask the AI: "Make a tool that shows my disk space." See Let the AI make tools.
- Write a pack file in a text editor. See Writing packs by hand.
All three make the same kind of pack file, so you can mix them: make a tool in the editor, then fine-tune it by hand, or the other way around.
What happens when you save
Your AI apps can use a new or changed tool right away, without restarting. SolutionMCP notices the change and tells connected AI apps the tool list changed.
Safe by design
Values the AI sends can't sneak in their own commands: in a program's arguments they're passed one by one, in scripts they're quoted for the script's language, and in web addresses they're encoded. File and folder parameters are checked against your allowed folders. See Programs, scripts and web requests.