Connect SigNoz to VS Code
Query logs, metrics, traces, alerts, and dashboards. Add Toolspoke to VS Code once and it can use 10 SigNoz actions. Your SigNoz credential stays in Toolspoke, and you choose which actions VS Code may call.
Set it up in VS Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to VS Code
.vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }Approve the authorization request when VS Code opens it.
Install SigNoz and connect it
Add SigNoz to a project in your Toolspoke workspace.
API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- API key
- SigNoz → Settings → Service Accounts → create an account, then generate a key on its Keys tab. Requires the Admin role.
- Instance URL
- Your SigNoz Cloud URL, or the base URL of your self-hosted install.
Choose what VS Code may do
All 10 actions only read, and any of them can be switched off for a project.
What you can ask VS Code for
A few of the SigNoz actions that only read, so they are safe to try first.
- Fetch raw log records matching a filter, newest first
- Aggregate logs into counts or percentiles, optionally grouped by attribute
- Fetch raw spans matching a filter, newest first
- Aggregate spans into latency percentiles, call counts or error counts, optionally grouped by attribute
What VS Code can do in SigNoz
10 actions read.
Reads
Query logs
Fetch raw log records matching a filter, newest first. Use this to read the actual log lines around an incident; use aggregate_logs when you want counts or rates instead.
Aggregate logs
Aggregate logs into counts or percentiles, optionally grouped by attribute. Use this for questions like "how many errors per service in the last hour" rather than pulling raw lines.
Query traces
Fetch raw spans matching a filter, newest first. Use this to find slow or failing requests; filter on has_error = true for errors, or parent_span_id = '' for root spans only.
Aggregate traces
Aggregate spans into latency percentiles, call counts or error counts, optionally grouped by attribute. Use expressions like p99(duration_nano) or count() with group_by ["service.name"] to build a service overview.
Query metrics
Query a named metric as a time series or a single value. timeAggregation collapses points within one series, spaceAggregation merges series together, for a counter use rate + sum, for a gauge use avg + avg.
Query promql
Run a raw PromQL expression against SigNoz's metrics store and return the time series. Use this when a query is easier to express in PromQL than through query_metrics, e.g. rate() over a counter joined with a recording rule.
List field keys
Discover the attribute names available for a signal, optionally matching a search string. Call this before writing a filter expression so you use attribute names that actually exist in this instance.
List services
List the service names SigNoz has trace data for. Use this to get the exact service.name values to filter traces and logs on.
List alerts
List the configured alert rules with their current firing state. Use this to check what is alerting right now, or to find a rule's id before inspecting it.
List dashboards
List the dashboards defined in this SigNoz instance with their ids. Use this to find a dashboard id, then open it in the UI, the full panel definitions are not returned.
SigNoz in VS Code: questions
Does VS Code see my SigNoz credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. VS Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Will 10 actions crowd VS Code's context?
No. Toolspoke shows VS Code five bridge tools, plus a guide where a toolkit has one, and VS Code searches for the SigNoz action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Where do the tools show up in VS Code?
In chat, in agent mode, which is where VS Code uses MCP servers. Add the block to .vscode/mcp.json for one workspace, or use the MCP: Add Server command.
What does it cost?
Tool calls are free on every plan, and a SigNoz call does not run in a sandbox, so it bills nothing.
SigNoz in your other apps
More observability toolkits for VS Code
Try SigNoz in VS Code
Free to start, and tool calls cost nothing on any plan.