Integrations · public documentation
Documentation.
Three interfaces share one set of business rules. REST, MCP and WebMCP call the same use cases; authorization, tenant isolation and concurrency are enforced on the server.
An agent cannot select another workspace.
Start here · Claude Code and Codex
Install the skill before connecting
Connecting MCP hands the agent the tools, but the skill is what tells it when to use them, which workspace to write to, how to avoid duplicating a task, and that recording a pending item does not authorize executing it. Without it, a connected agent usually ignores the service.
In Claude Code, with no clone
For Codex, or to install from a clone of the repository, use the install script described in the skills README.
/plugin marketplace add thalesholleben/backlog-syntax-oss
/plugin install backlog-cloud@backlog-syntaxHTTP · stable contract
REST API
Server integrations, automation and agents that need an explicit HTTP contract.
Quick start
- 1. Create a service account in Settings → Agents and tokens.
- 2. Save the token shown once and send it as a Bearer token.
- 3. Use
If-MatchandIdempotency-Keyfor mutations.
curl "https://backlog-api.syntaxlab.com.br/v1/workspaces/WORKSPACE_ID/tasks?limit=20" \
-H "Authorization: Bearer $BACKLOG_TOKEN"Remote · OAuth
MCP
AI clients use typed tools, leased claims and auditable events within a workspace.
Connect a client
Add the remote endpoint below to an OAuth-compatible MCP client. The flow uses PKCE, shows scopes before consent and issues separate authorization for the client.
- context and listing
- create and update
- claim, extend and release
- handoff and events
Remote endpoint
https://backlog-api.syntaxlab.com.br/mcpFor scripts without an MCP client, use the REST API with a service account token.
Browser · optional
WebMCP
Agents in supported browsers receive contextual tools for the open page.
How it works
The app detects document.modelContext. If this experimental API exists, it registers tools limited to the open project; otherwise, the human interface works as usual.
WebMCP provides contextual convenience. Remote MCP remains the primary integration for agents.
list_taskscreate_taskupdate_task_statusschedule_task
