Spanly MCP
Tools
The full surface of tools exposed by the Spanly MCP server.
The Spanly MCP server exposes the tools below. All of them resolve
against projects your signed-in account can access. Time-range arguments
accept the presets 5m, 30m, 1h, 3h, 1d, 7d, 30d, 90d,
180d, 365d. Anywhere a tool takes an environmentId, you can list valid
values with list_environments.
| Tool | Purpose |
|---|
list_projects | Projects accessible to your account. |
list_environments | Environments (regional contexts) inside the project. |
The leaf entity: one JSON-RPC request/response pair captured from your
MCP server.
| Tool | Purpose |
|---|
list_requests | Filter requests by server, client, method, status, and time range. |
get_request | Fetch a single request by id, including raw payload. |
aggregate_requests_by_method | Group request counts by method. |
| Tool | Purpose |
|---|
list_servers | Servers seen in the time range, with request counts and error rates. |
aggregate_servers | Roll up traffic by server name/version. |
client_calls_over_time | Time series of calls by client name/version. Useful for spotting client-side regressions. |
| Tool | Purpose |
|---|
list_errors | Errored requests in the time range. |
aggregate_errors_by_code | Counts grouped by error code. |
get_errors_by_code | Pull the underlying requests for one error code. |
The findings shown on the Issues tab: problems detected in live
traffic, plus static tool-manifest issues.
| Tool | Purpose |
|---|
list_issues | Runtime issues detected in live traffic (open plus recently resolved). |
list_static_scan_issues | Issues found by statically scanning a server's advertised tool manifest. |
list_issue_checks | Per-check summary: open and all-time counts, last activity, and fixability. |
| Tool | Purpose |
|---|
list_users | End users seen calling your servers, with session, request, and error counts. |
get_user | Aggregated activity for a single end user by endUserId. |
get_identity_settings | The environment's end-user identity configuration (secrets omitted). |
The same views that power the dashboard UI.
| Tool | Purpose |
|---|
dashboard_stats | Headline numbers: total requests, error rate, p50/p95/p99. |
dashboard_top_servers | Top servers by traffic. |
dashboard_top_tools | Top tools (MCP tools/call) by traffic. |
dashboard_slowest_operations | The slowest operations in the window. |
| Tool | Purpose |
|---|
get_integration_instructions | Returns copy-paste integration instructions for the TS SDK, Python SDK, CLI, or Docker. The same content as the in-app onboarding flow. |
Manage the channels that receive a notification when a new Issue
opens. Each channel opts in with notifyOnNewIssues and gates delivery by
minIssueSeverity.
| Tool | Purpose |
|---|
list_alert_channels | List notification channels (EMAIL, SLACK, WEBHOOK, IN_APP). |
create_alert_channel | Create a new channel, optionally with new-Issue notification settings. |
update_alert_channel | Update a channel's destination, auth, or new-Issue notification settings. |
delete_alert_channel | Delete a channel. |
| Tool | Purpose |
|---|
list_shared_links | Existing share links for the project. |
create_shared_link | Create a read-only link to a dashboard, request, or chart. |
revoke_shared_link | Revoke an existing link. |
Read the configuration and health of the hosted Gateway
reverse proxy that fronts your MCP server.
| Tool | Purpose |
|---|
get_gateway | The environment's gateway config (upstream, capture/auth modes, rules). |
get_gateway_health | Current upstream health (up / down / unknown, last error). |
list_gateway_domains | Custom domains attached to the gateway, with verification and TLS status. |
list_gateway_client_keys | Client auth keys issued for the gateway (key values omitted). |
Inspect and drive Mend: manifest patches, A/B canaries, and the
shims (applied patches) they promote to.
| Tool | Purpose |
|---|
mend_server_manifests | Live tool manifests per server (author custom patches against real tools). |
mend_list_patches | Manifest patches for the environment, optionally filtered by status. |
mend_create_custom_patch | Author a hand-written manifest patch (rename/hide tools, rewrite copy). |
mend_apply_patch | Apply a patch to every session immediately, skipping the canary. |
mend_launch_canary | Launch an A/B canary for a proposed patch. |
mend_list_canaries | Canaries for the environment (running and concluded). |
mend_get_canary | Full detail for one canary: patch, per-arm metrics, gate board. |
mend_stop_canary | Stop a running canary and roll back to the original manifest. |
mend_promote_canary | Promote a winning canary so its patch applies to every session. |
mend_list_shims | Applied patches (shims), including those awaiting an upstream patch. |
mend_activity | Recent Mend activity: proposals, canary launches, shim installs. |
- Read-only by default: every tool documents whether it mutates
state. Write tools act with your account's permissions.
- No pagination cursor surprises: listing tools take a plain
limit rather than opaque cursors, so an agent can plan multi-step
scans deterministically.
- Explicit ids:
create_* tools return the new entity's id;
get_*, update_*, and delete_* tools take it as an argument.