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.

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, apps, 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 Apps (list_apps)	List all apps in your workspace with their IDs and names. Returns app IDs, names, and direct links. Use get_app_details for full information, or explore_data to query an app's data directly with natural language.
Get App Details (get_app_details)	Return full details about an app, 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 App Queries (get_app_queries_tool)	Retrieve saved SQL queries for a specific app. Returns query names, descriptions, SQL, referenced tables, and whether they use cross_revisions (historical view). Use list_apps first to find the app_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 app 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.

Example prompts

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

Explore your environment (explore_data)

What data sources do I have connected?

Investigate access (explore_data)

Who has admin access across my cloud accounts?

Review posture (explore_data)

What are the most critical misconfigurations in my AWS environment?

Analyze identity (explore_data)

Which users have not logged in for more than 90 days? 

Check compliance (explore_data)

Show me all resources that are out of compliance with our policies.

Run a specific query (execute_sql)

Run the following SQL:
SELECT name, region, public_access_block_enabled
FROM aws_s3_bucket
WHERE public_access_block_enabled = false 

Ask your AI to write and execute (execute_sql)

Write and execute an SQL query that shows all IAM users who have not logged in for more than 90 days.

Connecting your client

To connect your client, you'll first need to generate a Personal Access Token (PAT) to authenticate your MCP client with Sola.

Generate a Personal Access Token

1. From your Sola workspace, go to Settings > Privacy and Security > Personal Tokens.

2. Click Generate Token.

3. Copy your Client ID. IMPORTANT: It is shown only once and cannot be retrieved later.

Workspace scope

Each token is linked to a single workspace. The MCP can only access one workspace per connection.

App permissions

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

Connect Your Client

Claude

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

2. Add the name and server URL:

Name: Sola
Remote MCP server URL: https://api.sola.security/mcp

3. Click Advanced settings, add your client ID in the OAuth Client ID, and click Add.

Claude Code

Cursor

Other

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

{
   "mcpServers": {
     "sola": {
       "type": "http",
       "url": "https://api.sola.security/mcp"
     },
	"oauth": {
        "clientId": "YOUR_CLIENT_ID"
     },
	"headers": {
       "x-create-resources": "true"
     }
   }
 }