mcpstat for Visual Studio CodeMonitor Model Context Protocol (MCP) tool, prompt and resource usage, errors and latency directly in VS Code. See which handlers run, which fail, and which have no recorded calls. Requires VS Code 1.100+ and a server instrumented with mcpstat 0.3.0. The dashboard reads that server's statistics tool or its local SQLite database. It does not automatically track other MCP servers. InstallOpen Extensions (Ctrl+Shift+X on Windows/Linux, Cmd+Shift+X on macOS),
search for Or install from the terminal:
What you can see
Connect your MCP serverOpen the Command Palette (Ctrl+Shift+P on Windows/Linux, Cmd+Shift+P on macOS) and run mcpstat: Get Started for the setup walkthrough, or connect directly:
The dashboard uses VS Code's existing tool connection and authentication. The
statistics tool can have a custom prefix, such as The first statistics request may require approval in VS Code. Allow up to two minutes to approve it and receive the result. Editor connections start with manual refresh; use Refresh for another observation or Start auto-refresh for periodic updates. When you enable editor auto-refresh, the dashboard shows how to open Chat: Manage Tool Approval and pre-approve the selected statistics tool (without approval). Choose Start auto-refresh to continue or Keep manual refresh to cancel. The dashboard checks whether that command is available; VS Code does not expose saved approval grants, so it cannot check your approval status or change editor permissions. VS Code controls tool approvals and may ask on every invocation, depending on editor
version and organization policy. See the approval instructions.
A server can declare its statistics tool with Your server must expose its statistics through an MCP tool. The
integration guide
shows how to register If a server has no compatible statistics tool or returns an unsupported statistics payload, a dashboard notice links to that guide. Install mcpstat in the server's Python environment, configure tracking, register the statistics tool, and restart the server. The dashboard cannot determine installed packages remotely. Missing Chat or MCP controlsIf VS Code's built-in Chat or MCP controls are hidden, open Settings and search
See VS Code's AI settings reference.
Direct HTTP and database connections do not need the built-in Chat controls.
If the controls are visible but no statistics tool appears, start your server and
confirm that it registers Connect an HTTP endpointChoose Connect an HTTP MCP endpoint in the connection picker. Enter the server's
Streamable HTTP endpoint, for example Remote endpoints use HTTPS; local development endpoints can use HTTP on loopback. Enter bearer tokens in the password prompt, separately from the endpoint URL. Open a statistics database
The reader opens database schema 4 in SQLite read-only mode, including committed WAL data while the server runs, preserving its schema and statistics. SQLite may use its normal shared-memory coordination files. With Remote SSH, WSL or containers, the extension runs on the workspace extension host. The database and Python executable must be accessible on that host. Saved connectionsThe selected MCP tool, HTTP endpoint or database is remembered for this workspace. Open mcpstat: Open Dashboard after restarting VS Code to resume collection. HTTP bearer tokens are stored in VS Code SecretStorage. Disconnect Source clears the saved selection and its HTTP token; Connect MCP Server selects another source. Read the dashboard
The activity chart covers the whole selected source; filters affect the cumulative cards, rankings and table. Automatic refresh defaults to 15 seconds while the panel is visible. HTTP and database sources start automatically; editor tool connections start manually. Start auto-refresh and Pause auto-refresh apply to this session. At most 240 observations are retained in memory. Hiding or closing the panel pauses collection; disconnect, reload and Clear Dashboard History discard the chart history. The saved source remains available after a reload. Missing observations, counter resets and changed inventories break chart lines. Cumulative values cover the selected server's recorded activity across its clients. Charts cover the intervals observed by this dashboard. Statistics queries may themselves be tracked by the host server. An unused handler means zero calls in the available recorded history. Synchronize your server's registrations to include unused handlers in the catalog. Latency averages use measured samples; historical outcome and latency coverage is shown explicitly. A source exceeding 1000 handlers is labelled partial, and interval graphs are disabled. The table shows up to 200 matches; search and filters narrow it. Privacy and securityStatistics are processed in the extension host. The connection profile is stored per workspace, bearer tokens use VS Code SecretStorage, and chart history stays in memory. Scripts, styles and charts are bundled with the extension. Documentation links open when clicked. The extension does not add telemetry. README screenshots and badges are hosted by GitHub and Shields.io; VS Code may fetch them when you open the extension's Details page. MCP polling invokes the selected statistics tool. Direct HTTP connections use the official MCP client with origin-restricted requests and bounded responses. Optional database access uses read-only SQLite through your configured Python interpreter. Requests, execution, query time and history are bounded. Workspace Trust is required. Statistics may include handler names, descriptions and tags. Give access only to people who may inspect that server's activity, and authorize the statistics tool in the server. The dashboard uses that connection's permissions. SQLite access is read-only; MCP requests invoke the selected statistics tool under the server's control. See the security policy for private vulnerability reports. Commands and settingsOpen the Command Palette to run these commands:
Enable mcpstat: Show Sidebar for connection status, the last observed calls, errors and handler counts, and connection actions. The sidebar does not collect statistics in the background; automatic refresh still requires a visible dashboard. Feedback and supportReport an issue or suggest an improvement. Include the extension and VS Code versions, connection type, and steps to reproduce. mcpstat: Check MCP Discovery can copy a summary of versions and tool counts. Remove tokens, private endpoints, database paths and private handler names from anything you share. Integration and project links
The registry listing launches mcpstat's documentation/demo server. To monitor your application, connect the dashboard to the statistics tool of your instrumented server. Install from sourceSee contributor instructions to build a VSIX. Install it using Extensions: Install from VSIX. The extension bundles the official MCP client. See third-party notices for dependency licenses, including the MCP client (Apache-2.0) and Bootstrap Icons (MIT), including its bundled icon font, CSS glyphs and logo artwork. The bundled notices retain the dependencies' full license texts and copyright notices. The included MIT license applies. Copyright (c) 2026 Vadim Bakhrenkov. Model Context Protocol is a trademark of LF Projects, LLC. Visual Studio Code and VS Code are trademarks of Microsoft Corporation. This independent project is not affiliated with or endorsed by LF Projects, LLC or Microsoft. |
