Skip to main content
A model does its work through tools: it reads and edits files, runs programs, sends mail and delegates. Stampede ships a set of native tools and can add the tools of any MCP (Model Context Protocol) server you configure. Which tools a given run may use is decided by its person’s preset or, for your own console turns, by the [tools] section (see Persons).

Native tools

The file tools stay inside the configured read and write roots unless the run has full access. run_command has no shell: the command line is split on spaces, quotes keep spaces inside one argument, and an unquoted |, &&, ; or redirect is refused. Which programs may start depends on whose run it is; see Presets. Command time limits are on Budgets and timeouts. Mail and rooms are on Mail and task rooms, delegation on Sub-agents.

Adding an MCP server

Each [[mcp]] table in ~/.stampede/config.toml launches one server as a subprocess. Its tools join the model’s set, each name prefixed with the label and two underscores (github__search_issues).
Put [[mcp]] tables below the top-level keys. The values of the env_passthrough variables come from the environment or the env file, as model keys do:

Environment of a server

A server starts with a cleared environment: only PATH, HOME, LANG, LC_ALL, TMPDIR, USER and TERM, plus exactly the variables named in its env_passthrough. A third-party server cannot read Stampede’s model keys, and a token passed to one server reaches only that server.

Checking a server

Configuration is read at startup, so restart after adding a server. Then check it:
doctor shows an mcp LABEL row per server: whether the command resolves, whether every env_passthrough name is set (names only), and a probe that launches the server and reports its tool count within 30 seconds. stampede doctor --offline skips the probe. A server that fails to start during a run is reported and skipped; the run goes on without its tools. Restart the workers so gateway, schedule and node runs see the server too:

MCP tool access

A server runs with your rights from the moment it starts, before any tool policy applies. Adding a server or changing what it runs is therefore your edit to the file. The agent’s save_mcp_server tool can re-save a server you already configured, unchanged, and refuses a new label or a different command, args or env_passthrough. A free person may use every MCP tool. A bounded person uses an MCP tool only when its policy names that tool exactly:
A person’s sub-agents use the same MCP tools from the same running servers. A sub-agent started where no person is involved (your own console turn, a headless stampede agent) runs no MCP tool.

Git host credentials

Commands and MCP servers both run with the cleared environment above, so a token in ~/.stampede/env does not reach gh, git or glab. Sign those tools in as the service user instead:
That login is held in the user’s files, so every allowed command a run starts can read it. Use a fine-grained, short-lived token limited to the repositories the person needs.