oci ghcr.io/wyre-technology/syncro-mcp:v1.4.7stdioApache-2.0updated 7d ago
A Model Context Protocol (MCP) server for Syncro MSP, implementing a decision tree architecture for efficient tool navigation.
What can you do with Syncro?
Syncro MCP Server
A Model Context Protocol (MCP) server for Syncro MSP, implementing a decision tree architecture for efficient tool navigation.
One-Click Deployment
Operator note — GitHub Packages authentication (required for one-click deploys). This server depends on the private
@wyre-technology/node-syncroSDK, which is hosted on GitHub Packages. GitHub Packages requires an authentication token on every install (no anonymous reads, even for public packages), so the cloud builders fail duringnpm installwith401 Unauthorizedunless you supply a token. Create a GitHub Personal Access Token with theread:packagesscope and provide it to the builder:
- Cloudflare Workers — set a build/environment variable named
NODE_AUTH_TOKENto your PAT.- DigitalOcean App Platform — set a build-time secret named
GITHUB_TOKENto your PAT.For local
npm install, runexport NODE_AUTH_TOKEN=$(gh auth token)first.
Features
- Decision Tree Architecture: Tools are organized by domain and loaded lazily
- Domain Navigation: Navigate between customers, tickets, assets, contacts, and invoices
- Lazy Loading: Domain handlers and the Syncro client are loaded on-demand
- Full Syncro API Coverage: Access to key Syncro MSP functionality
- Interactive Ticket Card (MCP Apps):
syncro_tickets_getrenders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Add comment" round-trip viasyncro_tickets_add_comment(internal-only by default); plain-JSON behavior is unchanged in other hosts. The card is neutral by default, brandable viawindow.__BRAND__injection orMCP_BRAND_*env vars (MCP_BRAND_NAME,MCP_BRAND_LOGO_URL,MCP_BRAND_PRIMARY_COLOR,MCP_BRAND_ACCENT_COLOR,MCP_BRAND_BG,MCP_BRAND_TEXT) — no rebuild needed.
Installation
WYRE MCP servers are distributed via OCI/GHCR images and (where available) MCPB bundles. The npm package
@wyre-ai/syncro-mcpis also published to GitHub Packages (npm.pkg.github.com); installing it requires an authenticated.npmrcwithread:packagesscope (runexport NODE_AUTH_TOKEN=$(gh auth token)locally).
Option 1: WYRE MCP Gateway (Recommended)
Use the hosted gateway at mcp.wyre.ai — paste your Syncro API key into the gateway UI and you're done.
{
"mcpServers": {
"syncro": {
"type": "http",
"url": "https://mcp.wyre.ai/v1/syncro/mcp",
"headers": {
"X-Syncro-Api-Key": "${SYNCRO_API_KEY}"
}
}
}
}
Option 2: Claude Code CLI (run from GitHub)
claude mcp add syncro \
-e SYNCRO_API_KEY=your-api-key \
-e SYNCRO_SUBDOMAIN=your-subdomain \
-- npx -y github:WYRE-AI/syncro-mcp
Option 3: Docker (GHCR)
docker run --rm \
-e SYNCRO_API_KEY=your-api-key \
-e SYNCRO_SUBDOMAIN=your-subdomain \
ghcr.io/wyre-ai/syncro-mcp:latest
Option 4: From Source
git clone https://github.com/WYRE-AI/syncro-mcp.git
cd syncro-mcp
npm ci
npm run build
node dist/index.js
Configuration
Set the following environment variables:
| Variable | Required | Description |
|---|---|---|
SYNCRO_API_KEY |
Yes | Your Syncro API key |
SYNCRO_SUBDOMAIN |
No | Your Syncro subdomain (if applicable) |
Getting Your API Key
- Log in to your Syncro MSP account
- Navigate to Settings > API Tokens
- Generate a new API token with appropriate permissions
Architecture
Decision Tree Navigation
The server uses a hierarchical approach to tool discovery:
- Initial State: Only navigation and status tools are exposed
- After Navigation: Domain-specific tools become available
- Back Navigation: Return to the main menu to switch domains
This reduces cognitive load and improves LLM tool selection accuracy.
Available Domains
| Domain | Description | Tools |
|---|---|---|
customers |
Manage customer accounts | list, get, create, search |
tickets |
Manage support tickets | list, get, create, update, add_comment |
assets |
Manage configuration items | list, get, search |
contacts |
Manage customer contacts | list, get, create |
invoices |
View and manage billing | list, get, create, email |
Tools Reference
Navigation Tools
syncro_navigate
Navigate to a domain to access its tools.
{
"domain": "customers" | "tickets" | "assets" | "contacts" | "invoices"
}
syncro_back
Return to the main menu from any domain.
syncro_status
Show current navigation state and credential status.
Customers Domain
syncro_customers_list
List customers with optional filters.
{
"query": "search term",
"business_name": "Company Inc",
"email": "contact@example.com",
"include_disabled": false,
"page": 1,
"per_page": 25
}
syncro_customers_get
Get a specific customer by ID.
{
"customer_id": 123
}
syncro_customers_create
Create a new customer.
{
"business_name": "Acme Corp",
"firstname": "John",
"lastname": "Doe",
"email": "john@acme.com"
}
syncro_customers_search
Search customers by query string.
{
"query": "acme",
"limit": 25
}
Tickets Domain
syncro_tickets_list
List tickets with optional filters.
{
"customer_id": 123,
"status": "Open",
"user_id": 456,
"resolved": false
}
syncro_tickets_get
Get a specific ticket by ID.
{
"ticket_id": 789
}
syncro_tickets_create
Create a new ticket.
{
"customer_id": 123,
"subject": "Network Issue",
"problem_type": "Network",
"comment_body": "Initial description"
}
syncro_tickets_update
Update an existing ticket.
{
"ticket_id": 789,
"status": "Resolved",
"user_id": 456
}
syncro_tickets_add_comment
Add a comment to a ticket.
{
"ticket_id": 789,
"body": "Comment text",
"hidden": false
}
Assets Domain
syncro_assets_list
List assets with optional filters.
{
"customer_id": 123,
"asset_type": "Desktop"
}
syncro_assets_get
Get a specific asset by ID.
{
"asset_id": 456
}
syncro_assets_search
Search assets by query or serial number.
{
"query": "workstation",
"asset_serial": "SN12345"
}
Contacts Domain
syncro_contacts_list
List contacts with optional filters.
{
"customer_id": 123,
"query": "john"
}
syncro_contacts_get
Get a specific contact by ID.
{
"contact_id": 789
}
syncro_contacts_create
Create a new contact.
{
"customer_id": 123,
"name": "Jane Smith",
"email": "jane@example.com"
}
Invoices Domain
syncro_invoices_list
List invoices with optional filters.
{
"customer_id": 123,
"status": "sent",
"since_date": "2024-01-01"
}
syncro_invoices_get
Get a specific invoice by ID.
{
"invoice_id": 456
}
syncro_invoices_create
Create a new invoice.
{
"customer_id": 123,
"due_date": "2024-02-01"
}
syncro_invoices_email
Email an invoice to the customer.
{
"invoice_id": 456,
"subject": "Your Invoice"
}
Rate Limiting
Syncro API has a rate limit of 180 requests per minute. The underlying @wyre-technology/node-syncro library handles rate limiting automatically.
Development
# Install dependencies. The @wyre-technology/node-syncro SDK lives on GitHub
# Packages, so authenticate first:
export NODE_AUTH_TOKEN=$(gh auth token)
npm install
# Build
npm run build
# Run in development
npm run dev
# Type check
npm run typecheck
# Lint
npm run lint
License
Apache-2.0
Install
Add Syncro to your client. Pick the one you use.
claude mcp add ghcr-io-wyre-technology-syncro-mcp-v1-4- -- docker run -i --rm ghcr.io/wyre-technology/syncro-mcp:v1.4.7codex mcp add ghcr-io-wyre-technology-syncro-mcp-v1-4- -- docker run -i --rm ghcr.io/wyre-technology/syncro-mcp:v1.4.7amp mcp add ghcr-io-wyre-technology-syncro-mcp-v1-4- -- docker run -i --rm ghcr.io/wyre-technology/syncro-mcp:v1.4.7{
"mcpServers": {
"ghcr-io-wyre-technology-syncro-mcp-v1-4-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/syncro-mcp:v1.4.7"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"ghcr-io-wyre-technology-syncro-mcp-v1-4-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/syncro-mcp:v1.4.7"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"ghcr-io-wyre-technology-syncro-mcp-v1-4-","command":"docker","args":["run","-i","--rm","ghcr.io/wyre-technology/syncro-mcp:v1.4.7"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"ghcr-io-wyre-technology-syncro-mcp-v1-4-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/syncro-mcp:v1.4.7"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"ghcr-io-wyre-technology-syncro-mcp-v1-4-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/syncro-mcp:v1.4.7"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"ghcr-io-wyre-technology-syncro-mcp-v1-4-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/syncro-mcp:v1.4.7"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"ghcr-io-wyre-technology-syncro-mcp-v1-4-": {
"type": "local",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/syncro-mcp:v1.4.7"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"ghcr-io-wyre-technology-syncro-mcp-v1-4-": {
"command": {
"path": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/syncro-mcp:v1.4.7"
]
}
}
}
}Add to your Zed `settings.json`.
docker run -i --rm ghcr.io/wyre-technology/syncro-mcp:v1.4.7Run `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation25/25
- Maintenance25/25
- Trust16/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 0 days ago
- Has a release history
- Repository is not archived
- Licensed Apache-2.0
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.4.7Latest | Aug 20, 2026 |
| 1.4.6 | Aug 13, 2026 |
| 1.4.5 | Aug 13, 2026 |
| 1.4.4 | Aug 10, 2026 |
| 1.4.3 | Aug 7, 2026 |
| 1.4.2 | Jul 25, 2026 |
| 1.4.1 | Jul 18, 2026 |
| 1.4.0 | Jul 17, 2026 |
| 1.3.2 | Jul 13, 2026 |
| 1.3.0 | Jun 2, 2026 |
| 1.2.6 | Jun 2, 2026 |
| 1.2.5 | May 22, 2026 |
| 1.1.6 | May 7, 2026 |
| 1.2.4 | May 7, 2026 |
| 1.2.3 | May 6, 2026 |