--web-search, --web-fetch, and --shell. You choose the capability once, and MeshAgent selects the provider-specific tool path that matches the model you are running.
Add built-in capabilities from the CLI
--web-search, --storage, --shell, or --document-authoring. --require-toolkit is the exception for attaching an external toolkit by name. The tables below show the current CLI flags for each built-in capability.
Run meshagent process join --help to see the current tool flags and related configuration options.
Built-in capabilities
Web and retrieval
Storage and memory
MCP and external tools
For setup paths such as Powerboards installs, MCP URL auto-discovery, and OpenAI connector manifests, see MCP Servers.
In the current
meshagent process runtime, MCP is exposed through --mcp rather than as a required named toolkit.
Shell and execution
--advanced-shell is the right choice when the agent needs to manage a working container across several steps instead of treating each shell command as an isolated call.
If the shell environment needs access to runtime metadata from the current room or service, add --shell-tool-config-mount <mount>. When the current runtime exposes MESHAGENT_SPEC_PATH or MESHAGENT_MEMBERS_PATH, MeshAgent mounts those runtime files into the shell container as spec.json and members.json under the target directory and points the env vars at the mounted paths.
Provider-native tools
Document and content tools
Discovery
If a built-in capability does not have a direct
meshagent process flag, add it from the SDK or package it into your own service or custom toolkit.