AI agents

Vexlo’s MCP server gives AI agents access to recorded code execution. An agent can inspect which functions ran, their arguments and return values, errors and retry attempts, and observed relationships between functions. It can use that evidence with the source, tests and other context available for its task. Connect Vexlo to the agent’s MCP client, then query the recorded data as needed. The same recordings are available through the web UI and HTTP API.

​

Execution as task context

Source code describes what a service can do. A recording shows what its instrumented functions did in one execution, including the data they received and returned. Function metadata connects those individual recordings to observed callers, callees and retained examples. An agent can start with a request identifier, a function, a service or a symptom. To examine a function, find its observed callers and inspect their executions. To explain an unexpected response, follow the calls and data that produced it.

​

Available evidence

A read token determines which teams the MCP server can query. Service and environment filters narrow those queries to the relevant deployment. Requested teams cannot expand the token’s access. Give the agent the available identifiers and scope along with the task, so it can find the right execution before interpreting its data.

​

From a question to recorded behavior

In the checkout investigation, an agent received an order identifier, an unexpected total and the relevant pricing rule. It searched for the recording, followed the pricing branch and read a successful discount call’s input and output. The customer had loyalty_member: true, but the function returned zero. Comparing that input with the supplied source identified a field-name mismatch. The graph also contained a recovered payment error; that error was separate from the incorrect price. The runtime data helped the agent locate the calculation before proposing a correction. Use execution data explains the query workflow and how to interpret the results. It also covers progressive disclosure for managing the agent’s working context. The MCP tool reference provides exact argument and response contracts.

​

Using the evidence

The agent’s host provides the tools for its wider task. Vexlo provides recorded execution; source inspection, code edits, test runs or other actions use the host’s other tools. In the checkout case, the agent proposed a source correction. A regression test and a new recording then verified that input case. Match recordings to the relevant application revision and check recording quality before relying on an absence or an apparent dependency. Observed usage is evidence of what ran; it does not enumerate every possible caller or input.