MCP tools
Every operation a connector exposes automatically becomes an MCP tool on that connection's MCP server. Which tools you get depends on the connector behind the connection your client points at — see MCP for the scoping model, the OAuth flow and how to connect a client.
Which connectors expose tools
Not every connector has callable operations. Some exist only to hold an OAuth connection, and those expose no MCP tools.
| Connector | Example tools |
|---|---|
| SSH | listFiles, readFile, tailFile, searchFile, getFileInfo, listDirectories |
| Google Sheets | getSheetValue, setSheetValue, clearSheet |
| OpenAI | prompt |
| Philips Hue | listLights, getLightState, setLightState, listDevices |
The full list
The connector catalog is generated from the live Services API at build time and lists every connector, every operation, and the full JSON Schema for each operation's arguments and response. It is the authoritative list — this page only orients you.
To discover the tools for one specific connection at runtime, call tools/list against that
connection's MCP endpoint, or GET /services/{adapterConnectionId}/capabilities over the HTTP API.
TODO: the catalog lists arguments and schemas but not effect — whether a tool reads, writes, deletes or invokes. That classification exists per operation in the API and reaches MCP clients as annotations. Surface it here, or in the catalog rendering, so a reader can see at a glance which tools mutate their data.