Skip to main content
Growth plan and above. Off by default — enable under Settings → Modules.
Connect Worksynk to an AI host so you can ask about your work in the tool you’re already using.

Supported hosts

Claude, ChatGPT, Grok, Cursor, VS Code and other MCP-compatible clients. There is no fixed list — anything that speaks MCP can connect.

Setting it up

1

Create a connection

In Worksynk, go to Settings → MCP and create a client for the host you’re connecting. You’ll get a client ID and a secret — the secret is shown once, so copy it now.
2

Choose its access

Tick read, write, or both. Read-only is the right default; see Access and limits.
3

Add the server in your AI host

Follow the walkthrough for your platform below. Settings → MCP shows the exact server and OAuth URLs for your workspace — copy them from there.
4

Authorize once

Approve the connection in Worksynk. You’re already signed in, so this is a single click — no second login.
The URLs and credentials are specific to your workspace, so they live in the app under Settings → MCP rather than in these guides. Copy them from there as you follow the steps below.

Per-platform walkthroughs

  1. Create a connection in Settings → MCP with platform “Claude”.
  2. Claude.ai: Settings → Connectors → Add custom connector.
  3. Claude Desktop: add the remote server in your connector settings.
  4. Paste the MCP server URL. Choose OAuth, and enter the client ID and secret.
  5. Approve on the Worksynk screen, then use the tools from any chat.
  1. Create a connection in Settings → MCP with platform “ChatGPT”.
  2. In ChatGPT, open Settings → Connectors (availability depends on your plan).
  3. Add a custom MCP server using the Worksynk server URL.
  4. Enter the authorization and token URLs shown in Settings → MCP, with the client ID and secret.
  5. Authorize once in the browser, then enable the connector in a chat.
  1. Create a connection in Settings → MCP with platform “Grok”.
  2. In Grok, open Settings → Connectors (or Custom tools).
  3. Add a remote MCP server and paste the Worksynk server URL.
  4. Enter the client ID and secret when prompted for OAuth.
  5. Complete the Worksynk approval, then ask Grok to use Worksynk tools.
  1. Create a connection in Settings → MCP with platform “Cursor”.
  2. Open Cursor Settings → MCP → Add new global MCP server.
  3. Add the Worksynk server URL to your MCP configuration.
  4. Complete OAuth when prompted, or use an API key from Settings → API keys for a simpler setup.
  5. Reload MCP servers and confirm the Worksynk tools appear.
  1. Create a connection in Settings → MCP with platform “VS Code”.
  2. Command Palette → “MCP: Add Server”, or edit your MCP config file.
  3. Add the Worksynk server URL as an HTTP server.
  4. Authenticate via OAuth or a bearer API key when prompted.
The same steps work for Windsurf, VSCodium, and other VS Code–based editors.
Worksynk isn’t limited to a fixed platform list. Point any MCP-compatible client at the server URL from Settings → MCP. Hosts that support dynamic registration can register themselves; machine-to-machine clients can use the client credentials grant with the ID and secret.

If the host asks how to send credentials

Some hosts ask which authentication method to use. Worksynk accepts all three; client secret post is the right choice in almost every case, and the one most connector UIs default to.

What a connection can do

Read your projects, tasks, notes, time and reports; and — if you grant write access — create and update work.

Access and limits

A connection acts as the person who authorized it and can never see or do more than they can.
Grant read-only unless the assistant genuinely needs to change work. Write access executes immediately over MCP with no confirmation prompt.
Every tool call is recorded, so there’s a trail of what an assistant did.

Reviewing and revoking

Owners and admins can see every connection reaching the workspace — and every member API key — under Settings → MCP → Workspace access, and revoke any of them. Revoking takes effect immediately.