For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sola MCP

Bring your full security environment into any AI assistant

The Sola MCP (Model Context Protocol) server connects your AI assistant directly to your Sola workspace, giving you access to your security data, connected sources, and intelligence without leaving your workflow.

Use it to explore your environment, investigate security risks, and run queries using natural language, from any AI-powered tool.

Query your security data from any AI tool.

Sola MCP
Sola MCP

Supported clients

Claude, Claude Code, Cursor, OpenAI Codex, VS Code, and any MCP-compatible tools.

See how to connect your client below.

Security and permissions

The Sola MCP server provides read-only access to your Sola workspace, including your connected data sources, projects, queries, and vendor tables. Your data can never be modified through the MCP. Access is scoped to the workspace the token was generated in.

Available tools

The Sola MCP exposes the following tools to your AI assistant.

Tool
Description

List Projects (list_projects)

List all projects in your workspace with their IDs and names.

Returns project IDs, names, and direct links.

Use get_project_details for full information, or explore_data to query an project's data directly with natural language.

Get Project Details (get_project_details)

Return full details about an project, including integrations, connectors, vendors, tables, queries, canvases, and monitor rules.

Each vendor has integrations with statuses. Tables may be in different states per integration: syncing, disabled, or missing.

Get Project Queries (get_project_queries_tool)

Retrieve saved SQL queries for a specific project.

Returns query names, descriptions, SQL, referenced tables, and whether they use cross_revisions (historical view).

Use list_projects first to find the project_id.

Get Vendor Tables (get_vendor_tables)

Discover all vendor tables available in your workspace.

Optionally filter by vendor name.

Tables are populated by vendor integrations. Use this to see what data is available before running a query.

Get Vendor Schemas (get_vendor_schemas)

Get column-level schema details (names, types, descriptions) for specific vendor tables.

Use this to discover columns before writing SQL queries.

Execute SQL Query (execute_sql)

Run read-only SQL queries directly against your project data source tables.

Only SELECT statements are allowed, with safety validation.

Use this for specific queries.

For natural language exploration, use explore_data.

Explore Data (explore_data)

Ask natural language questions about your environment, security posture, compliance, and more.

Uses Sola's graph intelligence and security domain expertise for complex queries.

Also ideal when you want to explore in natural language without writing SQL.

Get Data Exploration Status (get_data_exploration_status)

Check the progress of a background explore_data job and return its final answer once complete. Use this to poll for results after calling explore_data.

List Risk Clusters (list_risk_clusters_tool)

List Lumina Signals in your workspace, with options to filter by severity and score. Use get_risk_cluster_detail for full details on a specific signal.

Get Risk Cluster Detail (get_risk_cluster_detail)

Return full details about a specific Lumina Signal, including its business context, blast radius, and recommended actions.

Example prompts

Here are a few examples of what you can ask your AI assistant using the Execute SQL Query and Explore Data tools.

Connecting your client

To connect your client, follow the steps below for your tool. When you connect, you'll be prompted to log in to Sola, or create a new account if you don't have one yet.

Workspace scope

Each connection is scoped to a single workspace. The MCP can only access one workspace at a time.

Project permissions

MCP actions on a project are limited by your role on that project. For example, if you have Viewer access on an project, Execute SQL Query will fail for that project.

Connect Your Client

1. From your settings, go to Connectors and click Add custom connector.

2. Add the name and server URL, and click Add.

1. Run the following command in your CLI:

2. Start a Claude session using the claude command and run /mcp to authenticate.

1. From your settings, go to Tools & MCPs.

2. Click on New MCP Server.

3. Add the following to your file and save:

4. Go to Tools & MCPs and connect the Sola MCP.

Update the mcp.json file for your client with the following:

Using a different MCP client? Contact us and our team will get you set up.

MCP settings

Configure the Sola MCP by adding headers to your config file. See example below.

Global

Settings
Description
Default

Create Resources

(x-create-resources)

When using Explore Data, controls whether Sola saves generated queries and canvases to your workspace.

false

Query

Settings
Description
Default
Max

Query Timeout

(x-query-timeout)

How long Sola waits before stopping a query.

300 (5 min)

600 (10 min)

Query Rows Limit

(x-query-rows-limit)

Maximum number of rows returned.

100000

100000

Query Memory Limit

(x-query-memory-limit)

Maximum size of the query response.

1048576 (1 MiB)

10,485,760 (10 MiB)

Example config with settings applied

Last updated

Was this helpful?