Skip to main content
TripleBits Apprentice - Software for Agents

Menu

Sign In Register

Bind MCP Tools To An Agent

Enable a global MCP server for one Apprentice agent, configure per-tool Allow Ask Deny policies, set secret overrides, and check runtime health.

17 views

Bind MCP Tools To An Agent

After installing an external MCP server globally, bind it to the agents that need it.

A binding decides whether one agent can use one MCP server and which discovered tools are allowed, asked, or denied.

Open Agent Bindings

Open the agent, then select Config > MCP Servers.

This tab shows globally configured MCP servers and the current binding state for the agent.

If no global MCP servers exist, open Settings > MCP Library and install one first.

Enable A Server For One Agent

Turn on the server binding for the agent.

Enabling the binding does not mean every tool should run automatically. After enabling, expand the binding and review tool permissions.

Choose Tool Policies

For each discovered tool, choose:

  • Allow: run automatically.
  • Ask: prompt before each tool call.
  • Deny: block the tool entirely.

Use Ask for new tools until you have seen real calls in Activity and Run Detail.

Use Deny for tools the agent should never use, even if they belong to an otherwise useful server.

Use Allow only for narrow tools with predictable behavior.

Use Bulk Actions Carefully

The binding row can set all tools to Allow, Ask, or Deny.

Use Set all: Ask as a safe starting point. Avoid Set all: Allow unless the server is low-risk and the agent's job is tightly scoped.

Secret Overrides

If a server has secrets, the binding can use global defaults or per-agent overrides.

Use overrides when:

  • One agent should use a read-only token.
  • Environments differ between agents.
  • You want separate service accounts.
  • A test agent should not use production credentials.

Runtime Health

The MCP Servers tab includes MCP Runtime Health.

Use it when a tool is not appearing, a server is excluded from a run, or the runtime state is failed.

Troubleshooting

If a server is not listed, install it in Settings > MCP Library first.

If tools are missing, refresh the MCP Servers tab or repair the global server.

If a tool prompts every time, set a narrower tool policy or saved permission only after reviewing the request.

If a tool is blocked, check External MCP Tools in Capabilities, the binding toggle, and the individual tool policy.

Next Step

After binding tools, run a small manual test before using the MCP server from schedules or integrations.