Use the dashboard

The Dashboard shows how your MCP servers are used and how your context performs. New accounts get a 30-day trial with Core, Action, and Predictive unlocked. After the trial, KPI cards, Calls Over Time, and Breakdown stay free; the request log requires Core.

Audience	MCP operators, support leads, product analysts
Prerequisites	At least one deployed MCP server and incoming tool calls from a client

Server list

The main dashboard page shows all your MCP servers with their status, total calls, and actions. Click any server to see detailed analytics.

Each server card also includes a three-dot menu for management actions, including deletion.

Delete an MCP server

Use the server card menu (...) and select Delete MCP server when a server is no longer needed.

Before deleting:

• Export usage and analytics data you need to keep.
• Remove the server from all connected clients (Cursor, Claude, VS Code, Windsurf, and others).
• Confirm no production workflow still depends on the server endpoint.

Deletion behavior:

• The MCP server becomes unavailable immediately for connected clients.
• It no longer counts toward your server limit, so deleting one server frees capacity right away.
• Deleted servers stay visible as Deleted cards and can be restored from the three-dot menu.
• Source and analytics data enter a 7-day self-serve restore window after deletion.
• If you restore within 7 days, access to the MCP server and analytics dashboard returns.
• After 7 days, data is permanently deleted and cannot be recovered.

Analytics overview

Each server dashboard includes:

Stats cards

Total calls, success rate, average latency, and active source count at a glance.

Tool usage breakdown

See which tools are called most frequently and their individual success rates. This helps you understand which tools deliver the most value.

Source activity

Understand which sources are queried most. If one source is rarely used, you might replace it with something more relevant.

MCP client connections

See which AI tools are connecting, such as Cursor, Claude Desktop, Windsurf, VS Code, and others. Use this data to understand where your context is used.

Calls over time

A 30-day chart of daily call volumes. Spot trends, peak usage periods, and growth.

Recent calls

The last 20 tool calls with full details: the query asked, tool name, sources referenced, response time, and status.

Managing sources

From the server dashboard, you can manage source context:

• Add a new source: Paste a URL to add it. Indexing starts as a background job.
• Remove a source: Click X next to any source.
• Refresh a source: Re-index with the latest content. Unchanged pages skip re-embedding. The button stays available while indexing is in progress (Restart indexing).
• View indexing status: See pending, indexing (with percent and page counts), complete, error, or stalled.

Server status

Status	Meaning
Active	All sources indexed, server fully operational
Indexing	Sources are being crawled and indexed in the background (server is still usable; closing the tab does not stop work)
Error	One or more sources failed to index