MCP Server

Triggerware includes a built-in Model Context Protocol (MCP) server. This allows MCP-compatible agents to inspect available connectors and execute SQL queries against your local Triggerware instance.

Agents typically use MCP to:

• discover available connectors
• inspect connector schemas
• check which connectors are active
• run SQL queries across those connectors

The server communicates over stdio, making it compatible with standard MCP clients.

---

Configuration

Add Triggerware to your MCP client configuration:

{
  "mcpServers": {
    "triggerware": {
      "command": "triggerware",
      "args": [
        "mcp"
      ]
    }
  }
}

Once configured, your MCP client can call Triggerware tools directly.

---

Available Tools

The following tools are available to MCP clients. If you’re a human, you don’t need to worry too much about these!

list-connectors

Returns all connectors available on the local machine.

Parameters: none

Returns: list of connector names

---

describe-connector

Returns metadata for a specific connector, including its signature.

Parameters

Name	Type	Description
name	string	The connector to describe

---

list-active-connectors

Returns the connectors currently active on the running Triggerware server.

Parameters: none

Returns: list of active connector names

---

execute-query

Executes a SQL query against the Triggerware server.

Parameters

Name	Type	Description
query	string	SQL query to execute

Example

SELECT name, email
FROM salesforce_contacts
WHERE region = 'US'

Results are returned as rows.