List the connectors a site can use
list_site_connectors
Lists the connectors installed in a site's workspace and whether each one is on for the site.
These are the connectors a site's chat uses while it builds. Each comes with its toolkitSlug, its name, enabled for whether it is on for the site, and usableByMe, which says whether you connected your own account for it.
The site's chat reaches a connector only when it is on for the site and connected by the person chatting, because connectors are per person. Installing a connector or connecting an account happens on the Connectors page or under Manage connectors in the chat's + menu, never with an access token, over MCP or the HTTP API.
A site can have up to 10 connectors on at once, and the response carries that ceiling as maxConnectors. See Connectors.
Request
Call it with a POST to https://api.modulify.ai/v1/list_site_connectors, sending the inputs below as a JSON object. The token needs the config:read scope.
It only reads and changes nothing, so retrying it is safe.
curl -X POST https://api.modulify.ai/v1/list_site_connectors \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"projectId":"PROJECT_ID"}'Over MCP, the same method is the list_site_connectors tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
projectId |
string | Yes | The site id. |
Response
Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.