MCP tools and Runtime context
RunMat's MCP surface translates a coding client's structured tool calls into authorized project and Runtime operations. The exact tool list depends on the connection, deployment, client, and active permissions.
Tool families can include project discovery, file listing and reading, bounded edits, source execution, run status and cancellation, stdout, workspace metadata, variable materialization, figures, and run history. A tool result is a snapshot at a point in time; files or Runtime state may change before the next call.
Runtime context is richer than source context. Workspace values can contain generated or loaded data, and figures can expose results not stored in the project. Grant these tools only when the task needs them. Prefer metadata and summaries before materializing large values.
MCP describes transport and tool schemas; it does not by itself establish correctness or permission. RunMat validates the connection and project boundary, while the AI client applies its own approval UX. Keep both current and review the tool name, arguments, target project, and execution location before approval.