> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/ai/agent-evidence/mcp-tools.md).

# Record without the Currents CLI

Record a session with the Currents MCP tools when the agent cannot run the currents command

Some agents cannot install npm packages, so they cannot run the Currents CLI. If the agent is connected to the [Currents MCP server](https://docs.currents.dev/ai/connect.md) and has a shell, it can still save its screenshots, traces and logs as a [session](https://docs.currents.dev/ai/agent-evidence.md), and give you one link to them. An agent with no shell cannot upload files: it can only report the screenshots and page snapshots it has, and say that it did not record a session.

## What you need

* The agent connected to the Currents MCP server, with permission to write runs (`runs:write`) and to create share links (`shares:write`). You approve these permissions when you connect the agent. See [Connect your agent](https://docs.currents.dev/ai/connect.md).
* A shell, to upload the files, for example with `curl`.

## Ask the agent

```
Use the Currents browser-evidence skill. Record the checkout bug at
http://localhost:3000 as a Currents session and give me the link.
```

The skill has the steps: the agent creates the session through the MCP server, uploads its files from the shell, and creates the share link.

Claude Code with only the Currents MCP server and a shell, sped up:

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-f7b50c1cd92ef8573dad8327c5bde8da429ff077%2Fterminal-mcp-tools.gif?alt=media" alt="A terminal: Claude Code calls currents-create-session with four files, uploads each file with curl, calls currents-create-share-link, and replies with the session and its share page link"><figcaption></figcaption></figure>

## What you get

The Markdown version lists the session, its commit and pull request, and a link to each file. For a trace, it has a short text summary with each action, page errors and console errors. Another agent can check the work from it without opening the files.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2Fgit-blob-86a3e0aa3ba439b46a8ce4c1bd61d6fcceb98bcf%2Fsession-markdown.png?alt=media" alt="The Markdown version of a session: status, git details, each attachment with its link and caption, and links to the trace digest, frames, snapshots and failed requests"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/ai/agent-evidence/mcp-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
