Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

Your connection path

Zendesk
Your AI
Stacksync MCP OAuth

Your assistant works through your Stacksync workspace and its available connections.

First request

“Plan a support reporting replica”

Stacksync MCP · Customer support

Zendesk MCP integration.

Plan Zendesk ticket reporting, inspect connector actions and diagnose support-data sync issues through Stacksync MCP. Ticket, comment and user sync support is documented; other object types may require access to be requested.

Connector actionsSync management
Start using Stacksync MCP Explore example prompts

01 / The connection

What Zendesk can do through MCP

Plan Zendesk ticket reporting, inspect connector actions and diagnose support-data sync issues through Stacksync MCP. Ticket, comment and user sync support is documented; other object types may require access to be requested. Choose an AI client below to get started with the Stacksync MCP server.

The server belongs to Stacksync. The available Zendesk operations depend on your connection, permissions, and connector modules.

Explore the Zendesk connector →
ClaudeClaude CodeChatGPTCodexCursorVS CodeWindsurfGemini CLI

02 / Capabilities

Zendesk capabilities through MCP

Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.

Sync management

Plan ticket and user syncs

Inspect available fields and prepare mappings for the supported ticket, comment and user objects.

Connector actions

Prepare ticket actions

Discover the Zendesk modules and required inputs before proposing a lookup or record change.

Sync management

Inspect support sync failures

Read current issues and mappings to identify which tickets or related records need attention.

03 / Setup

Set up your AI client

Connect the MCP server first. Then connect Zendesk using the requirements below.

Chat assistantClaude

Connect Claude on the web or desktop to Stacksync through a custom connector and browser sign-in.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • On a Claude Team or Enterprise account, an owner must first add Stacksync under Organization settings → Connectors.

  1. Add a custom connector

    Open Customize → Connectors, select + Add, then Add custom connector. Name it Stacksync and use the server URL below.

    https://mcp.stacksync.com/mcp

  2. Connect your Stacksync account

    Select Connect, complete the Stacksync sign-in in your browser and choose the default workspace. Clear Make changes on the consent screen if you only want read access.

  3. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗
TerminalClaude Code

Add the remote Stacksync server to Claude Code and authenticate from its MCP menu.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • Claude Code installed with the claude command available in your terminal.

  1. Add Stacksync over HTTP

    Run the command below. Add --scope user if you want the connection available across your projects.

    claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

  2. Finish browser sign-in

    Open Claude Code, run /mcp, select stacksync and complete the Stacksync sign-in. Choose the workspace you want requests to use by default.

  3. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗
Chat assistantChatGPT

Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • A ChatGPT account with Developer mode and custom MCP apps available. The Stacksync guide lists Plus, Pro, Business, Enterprise and Edu; workspace administrators can restrict access.

  1. Enable custom app setup

    Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.

  2. Create the Stacksync app

    Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.

    https://mcp.stacksync.com/mcp

  3. Enable Stacksync in your chat

    Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.

  4. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗
TerminalCodex

Configure Stacksync in Codex with a remote MCP URL and an explicit OAuth login.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • Codex CLI installed with the codex command available.

  1. Register the remote server

    Add the Stacksync endpoint to your Codex MCP configuration.

    codex mcp add stacksync --url https://mcp.stacksync.com/mcp

  2. Sign in with OAuth

    Run the login command and complete the Stacksync browser sign-in. Select a default workspace; restart your Codex session if the tools are not yet listed.

    codex mcp login stacksync

  3. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗
Code editorCursor

Use Stacksync from Cursor by adding a remote server to its MCP configuration.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • Cursor installed with permission to configure MCP servers.

  1. Add the server configuration

    Merge this stacksync entry into the mcpServers object in ~/.cursor/mcp.json. Preserve any servers you already use.

    {
  "mcpServers": {
    "stacksync": {
      "url": "https://mcp.stacksync.com/mcp"
    }
  }
}

  2. Connect from Cursor

    Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.

  3. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗
Code editorVS Code

Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • VS Code with Copilot Chat Agent mode available.

  1. Add Stacksync to VS Code

    Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.

    code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}'

  2. Start it in Copilot Chat

    Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.

  3. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗
Code editorWindsurf

Add Stacksync to Cascade with Windsurf’s serverUrl configuration and OAuth sign-in.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • Windsurf installed with Cascade and MCP configuration available.

  1. Open the MCP configuration

    In the Cascade panel, open the … menu and select Open MCP config file. Merge this entry into mcp_config.json without removing other servers.

    {
  "mcpServers": {
    "stacksync": {
      "serverUrl": "https://mcp.stacksync.com/mcp"
    }
  }
}

  2. Authorize the first connection

    Save the configuration. Cascade opens the Stacksync sign-in flow the first time it uses the server. Choose your default workspace.

  3. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗
TerminalGemini CLI

Connect the Gemini command-line client to Stacksync through remote HTTP MCP and browser authorization.

Before you start

  • A Stacksync account with access to the workspace you want to use.
  • Permission to add an external MCP server in your AI client.
  • Gemini CLI installed with the gemini command available. These instructions apply to Gemini CLI, not the Gemini web app.

  1. Register Stacksync

    Run the following command in your terminal to add the HTTP server.

    gemini mcp add --transport http stacksync https://mcp.stacksync.com/mcp

  2. Authenticate inside Gemini CLI

    Start Gemini CLI, run the command below and finish the Stacksync sign-in in your browser.

    /mcp auth stacksync

  3. Check your workspace

    Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.

Check the connection

Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Zendesk connection and capabilities.

Full setup documentation ↗

04 / Put it to work

Zendesk workflow prompts

Example prompts for Zendesk. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.

01
Sync management

Plan a support reporting replica

Inspect my Zendesk and database connections, supported ticket and user fields, and existing syncs. Propose a one-way reporting replica that preserves ticket and requester IDs. Keep comment bodies out unless I explicitly request them. Flag any organization fields that need additional connector access before saving or starting a sync.

What to expect

A ticket-reporting plan with explicit requester relationships and comment-data boundaries.

02
Connector actions

Prepare a ticket update

Inspect the available Zendesk actions and their forms for the ticket task I describe. If a matching lookup and update action exist, propose the exact ticket ID and fields to change, distinguishing internal notes from public responses if the action supports them. Otherwise explain the gap. Do not update or reply to the ticket yet.

What to expect

A verified ticket-action proposal with the target and visibility choices explicit.

03
Sync management

Review a ticket-comment sync problem

Inspect my Zendesk syncs and issues for ticket comments. Identify the affected mappings and parent ticket IDs, then propose a correction for permissions, field types or record links based on the returned evidence. Ask me to choose the recovery action before retrying, reverting or ignoring any records.

What to expect

An evidence-based diagnosis of comment sync failures and their parent-ticket relationships.

05 / Before you run

Requirements and limitations

What you need

  • Connect your AI client to Stacksync MCP, sign in and select the workspace before inspecting its resources.
  • Reuse an authorized app connection or open the secure connection link from Stacksync. Enter credentials in the connection form, never in the chat.
  • A Zendesk account with access to the ticket data and operations needed for the workflow.

What to account for

  • Available actions depend on the live connector catalog, your connected account and MCP Gateway Policies. Inspect the action and its form before using it.
  • The published connector lists Organizations, Attachments and Ticket Forms as on request. Do not treat them as generally available.
  • Ticket comments can contain sensitive content. Specify the required fields and access; syncing comments is not proof of a direct comment-posting action.

Your workspace. Your permissions.

OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.

Read about permissions and approvals ↗

If setup does not work

The MCP server does not appear
Check your client’s custom MCP settings and any plan or administrator prerequisites. Reconnect using the setup instructions above.
Your workspace or app is missing
Verify the Stacksync account and workspace selected during OAuth, then inspect the workspace’s connections. Add missing app credentials through the secure connection flow.
An action is unavailable or denied
Inspect the current connector modules and required inputs. Check your workspace role, read-only consent, gateway policy, and the source app’s API permissions.

06 / Common questions

Zendesk MCP questions

Can I sync Zendesk organizations and attachments?

The current documentation marks Organizations, Attachments and Ticket Forms as on request. Confirm access before designing a dependency on those objects.

Can an assistant send a public ticket reply through this page?

Only if the live connector exposes the required action and the account is authorized. The sample prompts request a proposal; they do not authorize a public reply or assume that comment sync support provides a sending action.

Is ticket sync the same as querying tickets in chat?

No. Sync tools inspect and manage the transfer configuration and issues. Direct ticket reads require a discovered connector action, or a separately authorized query against a synced database.

Reviewed · Product documentation and connector references

Keep building

Connect the rest of your stack.

CRM

Salesforce

Plan a Salesforce reporting replica

CRM

HubSpot

Plan a contact and company replica

ERP

NetSuite

Plan order reporting with line items

← All MCP connector guidesCreate your Stacksync account ↗