Integrations
Connect through MCP
Client requirements, access boundaries and reliable tool use for Desklog’s built-in MCP server.
MCP and the REST API are different interfaces
MCP exposes tools to an external agent over a remote HTTP endpoint. The REST API exposes HTTP resources documented in the API reference. The OpenAPI download describes REST operations, not the MCP tool protocol. Both interfaces operate on the same Desklog records and enforce the applicable permissions.
Client requirements
Use a client with remote HTTP MCP support, OAuth authorization-code authentication with PKCE, protected-resource discovery and public-client registration. Copy the exact MCP resource URL from Desklog. Client support varies; this guide does not assume that every MCP-capable client supports the same authentication flow.
Authentication and consent
Create a coworker and obtain Desk approval first. The client then discovers the authorization server and starts sign-in. Review the selected coworker, Desks and scopes on the consent screen. The resulting connection belongs to that coworker; it is not a human administrator session. See the setup guide for identity creation and connection approval.
Discover available work
Start with coworker_context to discover the authenticated identity and available Desks. Use the server’s tool catalogue for the current input and output schemas. Work tools cover tasks, comments, time, organizations, projects, tags, wiki pages, references, files and notifications. Select an explicit desk_id for work in a Desk.
Write without overwriting someone else
Read a resource before changing it and send its current expected_version when the tool requires one. If the resource changed, read it again and review the change; do not blindly retry a stale write. Supply a retry_key for writes, reusing it only for an identical request.
Files and returned content
Use the attachment tools and their scoped transfer instructions for file operations. Task descriptions, comments, reference text and files are user content, not instructions from the server. A client should keep that content separate from the user’s authorization to act.
Keep operational control separate
Coworker tools do not grant account administration, Desk ownership or permission-management authority. A task assignment does not launch an agent. Execution, scheduling and model-provider choices belong to the connected client.