dots.v2.actionGateway.mcpServers.byServer_ref().resync.post()
Generated on 13 Nov 2026
from DoTs version
v1.24.0
Usage
client.v2.actionGateway.mcpServers.byServer_ref(server_ref).resync.post(body: Mcp_server_resync, requestConfiguration?: RequestConfiguration<object>): Promise<undefined | Resync_mcp_server_response>Description
Connects to the server, lists its tools, and records them. Discovered tools are not callable until you enable them.
When discovery finishes in time, returns 200 with the server and its tools; a discovery failure is
reported in syncStatus and syncError rather than as an error. Otherwise returns 202 with pending
set while discovery continues: poll GET .../mcp-servers/{server_ref} until lastSyncedAt or
syncError changes (syncStatus is not reset while discovery runs).
For a server registered with credentialRefSource connection, user_id is required; if that user
has not authorized the server yet, the response carries authorization with the URL to send them to.
Resyncs are rate limited per team, and a team can run only a few discoveries at once; either limit
returns 429.
Parameters
Path Parameters
server_refstring requiredExample:
docsServer identifier (
serverRef) of one of your team's MCP servers.
Request Body
userIdstring optionalExample:
aliceRequired for a server registered with
credentialRefSourceconnection: discovery reaches the server as this user, through their connection, because such a server has no team-wide credential. Ignored otherwise.
Request Sample
Response Example
More Information
See /v2/action-gateway/mcp-servers/{server_ref}/resync in the API reference for additional detail on responses, headers, parameters, and more.