Skip to main content

spm-mcp — MCP server for Secure Proxy Manager

A Model Context Protocol server that exposes the Secure Proxy Manager management API as tools — so an assistant/agent (e.g. Claude) can inspect and drive your self-hosted Secure Web Gateway: query traffic and analytics, manage block/allow lists, toggle WAF rule categories, and reload config.

Tools

Tool What it does
spm_status, spm_dashboard health + summary totals
spm_top_domains, spm_shadow_it, spm_user_agents analytics (incl. shadow-IT / agent egress)
spm_recent_logs recent proxy access-log rows
spm_security_score posture score
spm_waf_categories, spm_list_domain_blocklist current WAF/list state
spm_block_domain, spm_unblock_domain mutate the domain blocklist
spm_toggle_waf_category mutate — enable/disable a WAF category at runtime
spm_allow_egress mutate — add to the egress allowlist
spm_reload_config mutate — apply pending changes

The server is read-only by default. The mutating tools are registered only with SPM_MCP_READONLY=false. The read tools return traffic data that anyone whose requests cross the proxy can shape (URLs, domains, user agents), so text in a log row can try to instruct the model; with the mutating tools available, an auto-approved call could disable a WAF category or open egress. Traffic output is wrapped in {"untrusted_data_notice": ..., "data": ...}, and every tool carries MCP annotations (readOnlyHint, destructiveHint) for the client's approval prompt. If you enable the mutating tools, do not auto-approve them.

Configure

Env Default Meaning
SPM_URL http://localhost:5001 SPM backend API base URL
SPM_USERNAME admin SPM admin user (Basic auth)
SPM_PASSWORD — SPM admin password
SPM_VERIFY true false to skip TLS verify for self-signed HTTPS
SPM_MCP_READONLY true false to also expose the mutating tools

Run

With uv (no install):

SPM_URL=http://localhost:5001 SPM_USERNAME=admin SPM_PASSWORD=... \
  uvx --from . spm-mcp

Or in Claude Desktop / any MCP client — add to the MCP servers config:

{
  "mcpServers": {
    "secure-proxy-manager": {
      "command": "uvx",
      "args": ["spm-mcp"],
      "env": {
        "SPM_URL": "http://localhost:5001",
        "SPM_USERNAME": "admin",
        "SPM_PASSWORD": "your-password"
      }
    }
  }
}

Or as a container (see Dockerfile) — an optional mcp service can be added to the stack's compose profile.

MIT-licensed, part of Secure Proxy Manager.

Metadata

Release files for spm-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for spm-mcp 0.2.0
File Size Uploaded Provenance
spm_mcp-0.2.0.tar.gz 5.1 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for spm-mcp 0.2.0
File Interpreter ABI Platform
spm_mcp-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 10.9 kB

Release files / spm_mcp-0.2.0.tar.gz

Download URL spm_mcp-0.2.0.tar.gz
Size 5.1 kB
Tags Source
SHA-256 checksum
How to use checksums
935afe906d8897f69fdb91009f4fca9abee931e8b1d4d06afb45fd47cab4bc40
BLAKE2b-256 checksum
How to use checksums
6932bf2fa351fd8aa9a0e6b8bb9f155bacd0d23e2bec66e98f5d21ed2ba89992
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Release files / spm_mcp-0.2.0-py3-none-any.whl

Download URL spm_mcp-0.2.0-py3-none-any.whl
Size 5.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f4ff522cb9d25cb049ca7a5600974606e5cf539287a243189ba648abcc194998
BLAKE2b-256 checksum
How to use checksums
12a70655be9869d5f8794146330bda8eef7535fd80bb27a2426402e8f02e0434
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

Security for spm-mcp 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for spm_mcp-0.2.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page