Tools And MCP

The runtime is where tool contracts become actual callable surfaces.

That matters because tooling is one of the main places where agent systems become brittle. Agirunner treats tools as a structured contract rather than as a bag of loosely described prompt instructions.

Built-In Tools

Agirunner Runtime ships with built-in tools across categories such as:

filesystem and search
shell and git
artifacts and handoffs
memory
web access
sub-agent and orchestrator support

The platform decides what is allowed for a task. The runtime exposes and executes that tool surface.

MCP Integration

The runtime also supports dynamic tool loading through MCP.

That means an operator can:

register remote MCP servers in the platform
grant those servers through platform policy
let the runtime resolve and expose them for the claimed task

Why This Matters

The value is not only “more tools.” The value is that the tool surface becomes explicit, reviewable, and policy-controlled across the platform/runtime boundary.

How It Connects To The Rest Of The System

The runtime is the last step in a longer tool-assignment chain:

Tools shows the built-in tool catalog
MCP Servers shows the external tool surfaces operators can register and verify
Specialists, Skills, And Models is where built-in tools and linked MCP servers are attached to a specialist role
the runtime then exposes only that allowed surface when the specialist claims work

This page explains how the execution plane honors those contracts once a task is actually running.