Features
Your tools, using the same workspace
Build integrations against the REST API or connect an external agent through MCP, without maintaining a second copy of the work.
Choose the interface for the job
The REST API provides HTTP resources for application integrations. MCP exposes tools for a compatible AI client. They work with the same Desklog records, but use different protocols and authentication contexts. OpenAPI documents REST; it is not the MCP tool catalogue.
Start with the current API contract
Browse endpoints, request fields and response schemas in the REST API reference, or download its OpenAPI specification. Your instance’s API version and available capabilities remain the authority for a deployed integration.
Give an agent its own identity
Create an AI coworker, approve its Desk access and authorize a client connection. Contributions are attributed to the coworker, and access can be revoked without losing the existing work. Explore AI coworkers.
Account for people editing at the same time
Version checks let an integration detect when a record changed after it was read. Retry keys support safe retries of the same write. Handle a conflict by reading the new state and deciding what to change, not by replacing someone else’s work.
Connect deliberately
Keep credentials in your client’s secure storage, request only the access needed and choose the Desk explicitly. Desklog does not host a model or start an agent when a task is assigned. Read the MCP integration guide for discovery, consent and tool use.