Log inSubmit server
Syncro logo

Syncro

Manage Syncro MSP customers, tickets, assets, contacts, and invoices through navigable MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Syncro

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "syncro": {
      "command": "npx",
      "args": [
        "-y",
        "github:WYRE-AI/syncro-mcp"
      ],
      "env": {
        "SYNCRO_API_KEY": "YOUR_VALUE_HERE",
        "SYNCRO_SUBDOMAIN": "YOUR_VALUE_HERE",
        "NODE_AUTH_TOKEN": "YOUR_VALUE_HERE",
        "GITHUB_TOKEN": "YOUR_VALUE_HERE",
        "MCP_BRAND_NAME": "YOUR_VALUE_HERE",
        "MCP_BRAND_LOGO_URL": "YOUR_VALUE_HERE",
        "MCP_BRAND_PRIMARY_COLOR": "YOUR_VALUE_HERE",
        "MCP_BRAND_ACCENT_COLOR": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

npx -y github:WYRE-AI/syncro-mcp

g/v12.2.0> npm notice Run `npm install -g npm@12.2.0` to update! npm notice npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@wyre-ai%2fnode-syncro - Not found npm ERR! 404 npm ERR! 404 '@wyre-ai/node-syncro@^1.0.5' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url. npm ERR! A complete log of this run can be found in: /home/user/.npm/_logs/2026-10-16T11_26_11_331Z-debug-0.log

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

The Syncro MCP server connects AI clients to Syncro MSP for customer, ticket, asset, contact, and invoice operations. It uses domain navigation and lazy loading so domain-specific tools appear after selecting a domain. Run it through the WYRE hosted gateway, Claude Code, Docker, or from source with a Syncro API key. Reach for it when an agent needs to query or update MSP service-management records.

Use cases

  • List customer accounts and contacts
  • Create and update support tickets
  • Search assets by serial number
  • Review and email customer invoices

Key features

  • Decision-tree domain navigation
  • Lazy-loaded Syncro tools
  • Customer and contact management
  • Ticket creation, updates, and comments
  • Asset search and lookup
  • Invoice creation and email delivery

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 42d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 23h ago via OSV.dev · github:WYRE-AI/syncro-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
Last commit4d agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Syncro works

What Syncro MCP server does

The Syncro MCP server exposes selected Syncro MSP operations through the Model Context Protocol. It covers five domains: customers, tickets, assets, contacts, and invoices. Depending on the domain, an agent can list, search, retrieve, create, update, add comments, or email invoices.

Customer tools support listing with filters, lookup by ID, creation, and text search. Ticket tools cover filtered listing, retrieval, creation, updates, and comments. Asset tools provide listing, lookup, and searches by query or serial number. Contact tools handle listing, retrieval, and creation. Invoice tools support listing, retrieval, creation, and emailing an invoice.

How it works

The Syncro MCP server uses a decision-tree navigation model rather than exposing every domain tool at once. At startup, navigation and status operations are available. An agent selects a domain with syncro_navigate, uses the tools loaded for that domain, and can return to the main menu with syncro_back. syncro_status reports the current navigation state and credential status.

Domain handlers and the Syncro client load on demand. This structure is intended to reduce the number of simultaneously visible tools and improve tool selection. The underlying Syncro API client automatically handles the documented limit of 180 requests per minute.

The ticket retrieval tool can render an interactive ticket card in MCP Apps hosts such as Claude Desktop and the web experience. The card supports an in-card add-comment round trip through the ticket comment operation. Other hosts retain plain JSON behavior. Card branding can be supplied through window injection or the documented MCP_BRAND_* variables.

Setup and configuration

Use the hosted WYRE MCP Gateway by configuring an HTTP MCP endpoint and passing X-Syncro-Api-Key with the API key. Local deployment options include the Claude Code CLI, the GHCR Docker image, and a source checkout built with npm.

Set SYNCRO_API_KEY to a Syncro API key generated under Syncro MSP Settings > API Tokens. SYNCRO_SUBDOMAIN is optional and applies when a subdomain is needed. Source and package installation require access to the private @wyre-technology/node-syncro SDK on GitHub Packages. Set NODE_AUTH_TOKEN for local npm installation; cloud builds need a read:packages token, with Cloudflare using NODE_AUTH_TOKEN and DigitalOcean using the build-time GITHUB_TOKEN secret.

For a source build, install dependencies, run npm run build, and start node dist/index.js. The repository also documents development, type-checking, and lint commands.

Tools and capabilities

Available navigation tools are syncro_navigate, syncro_back, and syncro_status. Domain tools include:

  • Customers: list, get, create, and search.
  • Tickets: list, get, create, update, and add a comment.
  • Assets: list, get, and search.
  • Contacts: list, get, and create.
  • Invoices: list, get, create, and email.

Most list operations accept filters such as customer ID, status, query, email, asset type, or date. Create and update operations accept the fields documented by the corresponding Syncro operation.

Limitations and notes

A valid Syncro API key is required. The optional subdomain setting may still be needed for accounts that use one. One-click cloud deployment is not install-and-run without GitHub Packages authentication because the private SDK requires a token on every package install.

Interactive ticket cards are host-dependent, while other hosts receive the regular JSON result. Syncro API usage is subject to 180 requests per minute, with rate limiting handled by the underlying SDK.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Syncro

Syncro is an MCP server that connects AI clients to Syncro MSP. Its main tools navigate customer, ticket, asset, contact, and invoice domains, then list, search, retrieve, create, update, comment on tickets, or email invoices. It uses a Syncro API key and supports hosted, CLI, Docker, and source deployments.

Install it through the WYRE hosted gateway, Claude Code CLI, GHCR Docker image, or from source. Local source setup requires cloning the repository, running npm installation, building with npm, and starting the compiled entry point. Package installation also requires GitHub Packages authentication for the private SDK.

Set SYNCRO_API_KEY to a Syncro API token. SYNCRO_SUBDOMAIN is optional and is used when applicable. For local or cloud package installation, NODE_AUTH_TOKEN or GITHUB_TOKEN may also be needed to authenticate to GitHub Packages, depending on the deployment method.

Yes, Syncro works with Claude Code through the documented CLI command. Configure the server with SYNCRO_API_KEY and, when applicable, SYNCRO_SUBDOMAIN, then run the GitHub-based command. Claude Desktop and the web MCP Apps experience can also render the interactive ticket card.

It can list, retrieve, create, update, and comment on Syncro tickets. Listing supports filters such as customer, status, resolved state, and user. The ticket retrieval operation can render an interactive card in supported MCP Apps hosts, while other clients receive plain JSON.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSyncro AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/syncro?style=directory)](https://allmcps.com/mcp/syncro)
HTML Embed
<a href="https://allmcps.com/mcp/syncro"><img src="https://allmcps.com/api/badge/syncro?style=directory" alt="Syncro on AllMCPs" /></a>