> For the complete documentation index, see [llms.txt](https://mcp-test-kitchen-docs.cakewalk.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mcp-test-kitchen-docs.cakewalk.security/reference/console.md).

# Console Reference

What each control in the console does, and which ones you need before a test run.

The console has two panes. **Scenarios** is where you choose what breaks. **Messages** is where you read what happened. You can drag the divider between them.

***

## Scenarios Pane

The pane opens on three tabs: **Tools**, **Resources** and **Prompts**. Scenario selection lives under Tools, and the controls below appear only while that tab is showing.

**Scenario picker.** Lists the six registered scenarios with their title, area and description.

**Customize.** Opens the parameters for the selected scenario. Params are a JSON object, and saving validates them: malformed JSON, anything that is not an object and null collections are all rejected. Omitted fields fall back to their defaults, and `{}` means all defaults. **Load example** inside the same dialog fills the box with working values. You often will not need it: picking a different scenario prefills that scenario's example for you, as long as you had not already edited the params by hand.

**Save.** Stores the selection against your account. It applies to your next session, not to a connection already open. The button stays disabled until your selection differs from what is already saved, and it stays disabled while the params are invalid. A dead Save button usually means one of those two, not a broken console.

**Terminate.** Closes your active scenario session and resets its invocation counters. Needed whenever you want an `onInvocation` test to start from zero.

{% hint style="warning" %}
**Terminate** renders only while the console believes a session is live, and that belief is a snapshot taken when the page loaded. Connect a client after opening the console and the button will not appear on its own. **Reload the page** and it is there.

Missing button therefore does not mean clean counters. It usually means the console has not noticed your client yet.
{% endhint %}

***

## Messages Pane

**Live entries.** New requests appear as they arrive, newest first, fifty to a page.

**Search and filters.** Narrow by date range, method, phase, category or caller. Method is an exact match. The caller filter narrows nothing while you hold one address, because your entries are already scoped to you.

**Detail drawer.** Click an entry for the recorded headers and the request params your client sent.

**Clear all.** Deletes your entries permanently. Run it at the start of a test so the log holds one run.

See [Reading the Record](/reading-the-record/record.md) for how to interpret what appears here.

***

## Before Every Test Run

Two clicks, in this order, and they do different things.

{% stepper %}
{% step %}

#### Terminate

Resets invocation counters. Reload the page first if you connected your client after opening the console, or the button will not be there.
{% endstep %}

{% step %}

#### Clear all

Empties the log.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Doing one without the other is the most common source of confusing results. A cleared log with a live counter looks like a fresh run and is not.
{% endhint %}

***

## Test Client

If you have no client to point at the server yet, the console generates a working TypeScript client already wired to the endpoint, with run instructions. It handles elicitation, so it can exercise the approval scenario.

C# and Python are listed and not available yet.

***

## Account Controls

**MCP access token.** The lock icon in the header. The dialog holds your personal access token and the full client configuration JSON, both ready to copy. **Regenerate** issues a new token and invalidates the old one immediately, so any client still holding it stops working.

**Feedback.** A form in the console. Rate limited to five submissions per ten minutes.

**Erase everything.** Deletes your observations, your saved scenario selection and your personal access token, and terminates your sessions. It is immediate and cannot be undone. You keep console access and get a new token the next time you ask for one.