Platform / MCP

Bring ThunderSaaS
into the AI clients you use.

Connect ChatGPT or Claude to ThunderSaaS through MCP. Let your preferred AI inspect the workspace data you authorize, using the same organization context and permissions that protect your business.

Connection direction

ChatGPT and Claude connect into ThunderSaaS.

MCP is an incoming connection to the ThunderSaaS MCP server. The external AI client connects to ThunderSaaS, asks for permission, and uses the approved read tools to work with authorized workspace data. This is different from an outbound integration where ThunderSaaS calls another service.

01External clientChatGPT or Claude starts an MCP connection request.
02AuthorizeA signed-in ThunderSaaS user reviews and approves access.
03ConnectThe client connects to the ThunderSaaS MCP endpoint.
04ReadThe client uses permission-aware tools to inspect workspace data.

What MCP enables

Ask your preferred AI about authorized business data.

Once connected, ChatGPT or Claude can discover the workspace context that the authorized user is allowed to see, inspect table structure, read records, and answer questions using supported queries.

Understand contextRead the connected session and organization context.
Discover dataList accessible tables and inspect their definitions.
Answer questionsRead records, filter results, and use supported aggregates.

Connect

Set up an incoming MCP connection.

  1. Open Workspace Settings. Go to the MCP section for the workspace you want to connect.
  2. Copy the MCP URL. ThunderSaaS provides the server endpoint at /mcp for the external client to use.
  3. Add it to ChatGPT or Claude. Start the MCP connection from the external AI client.
  4. Sign in to ThunderSaaS. The connection requires an authenticated ThunderSaaS session.
  5. Review the consent request. Confirm the provider, organization context, and requested read permission.
  6. Allow the connection. The external client receives an expiring access token and can begin using the MCP tools.

Read-only boundary

MCP can inspect data. It does not change your workspace.

The current ThunderSaaS MCP server exposes a read-only scope. It does not currently create, update, delete, import, export, configure applications, execute agents, or build apps.

Available now

Session details, table definitions, record reads, supported filters, and aggregate queries.

Not available through MCP

Record mutations, workspace configuration, workflow execution, application building, imports, and exports.

Need to change something? Use ThunderSaaS Commands, Agents, or Build with Prompts for operations that require writing or configuration.

Available tools

A small, permission-aware surface.

get_session_details

Return the authenticated ThunderSaaS user context.

list_table_definitions

List tables accessible to the user in the selected organization.

get_table_definition

Read metadata for an accessible table.

fetch_records

Fetch accessible records with optional status, limit, and offset values.

query_records

Use supported filters and operations such as count, list, select, sum, average, minimum, and maximum.

read_record

Read one accessible record using its table and record ID.

Access control

The connection follows your workspace permissions.

MCP does not grant access to every organization or every table. The connection is associated with the signed-in user and selected organization, and the available tools continue to use the user’s accessible workspace data.

User contextThe connection belongs to the ThunderSaaS user who approved it.
Organization contextAccess is tied to the organization selected during authorization.
Read scopeCurrent MCP access is limited to the supported read permission.

Security and lifecycle

Authorize once. Monitor and revoke when needed.

The connection uses OAuth authorization code flow with PKCE S256. Access tokens expire, connection use is tracked, and the user can revoke an active connection from Workspace Settings.

ActiveThe external AI client can use the approved read tools.
ExpiringThe token has a limited lifetime and the client must reconnect when it expires.
RevokedThe connection is disabled until a new authorization is approved.

Revoke access: open Workspace Settings → MCP, find the ChatGPT or Claude connection, and select Revoke.

Example

Ask ChatGPT or Claude about your workspace.

“Show me overdue invoices from this month.”

ChatGPT / Claude
↓ MCP read request
ThunderSaaS tables and records
↓ permission-aware result
A summary of the data you are allowed to see

The external AI client discovers the relevant table, applies a supported read or query operation, and summarizes the permitted results without receiving write access to the workspace.

Troubleshooting

When the connection does not work.

Authorization expired

Start the connection again from ChatGPT or Claude and complete the ThunderSaaS consent flow before the request expires.

Connection revoked

Review Workspace Settings and authorize a new connection if the external client should access the workspace again.

Table is unavailable

Confirm that the signed-in ThunderSaaS user belongs to the correct organization and can access the requested table.

Write request rejected

MCP is currently read-only. Use Commands, Agents, or Build with Prompts for changes and automation.

Read Integrations ↗Read Commands ↗Build agents ↗Build with prompts ↗