PlugsightDocs

Custom MCP server tools

Every Custom MCP server tool in the developer API, with its arguments and an example call.

Updated

Needs: A custom MCP server connection (Pro and Agency). Each of the server's own tools also becomes a tool, named after the connection. 1 tool.

These tools appear in GET /v1/tools only when the API key's MCP server includes a connection of this kind. Call each one with POST /v1/tools/\<name>, sending its arguments as a JSON object. See Calling tools for the request and response format.

Each tool of a custom MCP server is also a tool here, named after the connection and the server's own tool (for example notes__search_notes), with the server's own input schema. A tool counts as a change unless the server marks it read-only, and then takes "confirm": true (or "plugsight_confirm": true when the server's tool has its own confirm argument). Those tools differ for every server, so they aren't listed here: GET /v1/tools shows the ones your API key reaches.

Tool What it does Kind
custom_mcp_refresh_tools Refresh a custom MCP server's tools Read

The example requests fill in only the required arguments, with placeholder values.

custom_mcp_refresh_tools

Refresh a custom MCP server's tools · Read

Lists a custom MCP server's tools again now, instead of using the list Plugsight keeps for a few minutes, and says how many only read and how many make changes. If its tools changed, the AI app needs to reload Plugsight's tool list to see them.

Argument Type Required What it is
account string No Custom MCP server connection id from list_accounts (optional when there's only one)

Example request:

curl -X POST https://app.plugsight.app/v1/tools/custom_mcp_refresh_tools \
  -H "Authorization: Bearer $PLUGSIGHT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'