Saner MCP

The Saner Model Context Protocol (MCP) server gives AI-powered development tools direct access to the Saner CVEM API and Python SDK documentation. This enables developers to explore endpoints, generate SDK examples, and build integrations faster using natural-language prompts inside their editor.

The server is read-only. It serves API specifications and SDK documentation so your assistant can help you build integrations. It does not call the Saner API, does not hold your credentials, and cannot reach your Saner account.

Model Context Protocol (MCP) is an open standard that allows AI applications to securely access external tools, APIs, and documentation sources. By connecting your AI assistant to the Saner MCP server, the assistant gains contextual awareness of Saner APIs and can help generate accurate integration workflows in real time.

What MCP Enables

Once connected, MCP gives your AI assistant structured access to the Saner API documentation directly inside your development environment.

This allows you to:

discover Saner APIs without manually browsing documentation
search endpoint usage from within your editor
generate ready-to-use Python SDK examples
understand parameters and request structures instantly
explore the APIs covering organizations, agents, vulnerabilities, compliance data, and reports
build automation scripts using Saner APIs faster

Instead of switching between documentation and code, developers can interact with Saner APIs conversationally through their AI assistant.

Key Capabilities

Connecting to the Saner MCP server provides several powerful features:

Direct API Awareness Inside Your Editor

Your AI assistant understands available Saner endpoints and how they map to SDK resources and workflows.

Example:

Show me how to get organization details in Saner

Documentation Search from the Assistant

Search Saner documentation without leaving your coding environment.

Example:

What parameters are required for agent download in Saner?

Integration Code Generation

Generate working integration snippets instantly using supported SDK patterns.

Example:

Generate Python SDK code to export a vulnerability report in saner

Endpoint Discovery Assistance

Explore related APIs automatically.

Example:

Show APIs related to compliance management in saner

Supported AI Development Tools

The Saner MCP server works with any MCP-compatible AI client.

Commonly supported tools include:

Claude Code
Cursor
Windsurf
Claude Desktop
Other MCP-compatible development assistants

Once configured, these tools can access the Saner API and SDK documentation directly through the MCP server.

What the Server Does and Does Not Do

The MCP server does	The MCP server does not
Serve the complete OpenAPI specification for every Saner API endpoint	Call the Saner API
Serve Python SDK documentation and usage examples	Store or ask for your API key
Give your assistant everything it needs to write a working integration script	Connect to your Saner account or read your tenant data

Because the server never contacts Saner, anything your assistant reports about your environment
comes from a script you ran yourself, not from the MCP server.

Scripts your assistant writes run against your live Saner tenant. Endpoints that create, update,
delete, scan, or remediate make real changes. Review generated code before running it, and test
against a non-production account first where you can.

Why Use MCP with Saner ?

Using MCP significantly improves developer productivity by allowing AI assistants to:

understand Saner APIs automatically
generate correct SDK usage patterns
reduce documentation lookup time
accelerate automation development
simplify integration workflows

This enables faster and more reliable interaction with the Saner platform directly from your editor.