MCP Server
19 Tools.
Every CMS. Control Everything Through Claude.
The Syncific MCP server gives Claude full access to your creative asset pipeline. Browse, publish, optimize, and manage — all through conversation.
The Complete Tool Set
Check connected sources, active destinations, and account health
View recent syncs, deliveries, and operations
Schedule automatic publishing on intervals
View assets from Lightroom, Figma, Canva, Dropbox, Drive, and more
Sync and deliver assets to one or all destinations
See which assets are published where and when
Add, edit, and manage CMS connections
Group destinations for batch publishing
Verify a destination is reachable and authenticated
Generate alt text, titles, captions, and keywords
Create images from text prompts via OpenRouter
Compression reports and format recommendations
Review and approve optimization recommendations
Configure account, enrichment mode, and auto-optimize
Invite members and manage roles
Onboard new destination connections
Performance analytics, hero scores, and site audits
Event notifications to external services
Multi-workspace management for agencies
A Full Publish Sequence
Tool Reference: What Each Tool Does
Every tool Claude can call, with example prompts and what they return.
Returns platform health: connected sources, active destinations, pending syncs, storage usage, and subscription status. Use it when you want a quick overview of your Syncific account.
Example: "What is the status of my Syncific account?"
Lists assets from any connected source. Browse Lightroom albums, Figma frames, Canva designs, Dropbox folders, or Drive files. Returns asset names, thumbnails, dimensions, and modification dates.
Example: "Show me the latest photos in my Spring Collection Lightroom album"
The core publishing tool. Runs a sync diff to identify new or changed assets, then delivers them to selected destinations with automatic format optimization. Returns delivery status per destination.
Example: "Sync my Denver Architecture album to the Webflow and Contentful sites"
Shows the full source-to-destination mapping. Every asset that has been published, which destinations have it, when it was last synced, and whether the source has changed since. Essential for auditing what is where.
Example: "Which of my Lightroom photos are already on the WordPress site?"
Lists all connected CMS destinations with their type, URL, connection status, and asset count. Can also add, edit, or remove destinations.
Example: "List all my connected destinations and their status"
Manages destination groups for batch operations. Group client destinations together, set governance rules per group, and publish to entire groups at once.
Example: "Create a group called Client A with their WordPress and Shopify sites"
AI-powered metadata generation. Generates alt text, titles, captions, and keywords for any asset. Uses page context and GSC ranking queries when available for SEO-aligned descriptions.
Example: "Generate alt text for all images I just synced to WordPress"
AI image generation via OpenRouter. Creates images from text prompts with brand context. Generated images can be synced to destinations like any source asset.
Example: "Generate a hero banner for the spring collection landing page"
Returns compression reports: current format, file size, potential savings per destination format. Shows which assets would benefit most from optimization.
Example: "Which images on my WordPress site could be compressed further?"
Performance analytics powered by Google Search Console. Hero scores, A/B test results, CTR trends, and the Intelligence Optimizer audit queue.
Example: "Show me which assets are performing best on the Webflow site"
Manages automatic sync scheduling. Set intervals, choose which sources to monitor, and configure auto-publish rules. Assets sync without manual intervention.
Example: "Set up daily auto-sync from Lightroom to all destinations"
Review and approve or reject suggested actions from the Intelligence Optimizer. Each action includes rationale, confidence score, and estimated impact.
Example: "Show me pending optimization suggestions and approve the high-confidence ones"
Tests a destination connection by sending a 1x1 transparent test pixel through the full pipeline. Verifies authentication, format support, and API responsiveness.
Example: "Test the connection to my HubSpot destination"
Manages outbound event webhooks. Get notified when assets sync, when autosync runs, when errors occur. Configure endpoints, events, and signing secrets.
Example: "Set up a webhook to notify Slack when assets sync to production"
Platform configuration: account name, OpenRouter API key, enrichment mode, auto-audit settings, and auto-approve preferences.
Example: "Enable auto-audit with weekly re-crawls"
Team management: invite members, assign roles (viewer, editor, admin), and manage access across workspaces.
Example: "Invite sarah@agency.com as an editor on the Acme Corp workspace"
Connect Syncific to Claude in 3 Steps
Get your MCP server URL
Log into app.syncific.com, go to Settings. Your MCP server URL is displayed at the bottom of the page. Copy it.
Add to Claude
In Claude.ai, go to Settings, then Connectors. Click "Add Connector" and paste your Syncific MCP server URL. Claude will verify the connection.
Start publishing
In any Claude conversation, describe what you want to publish. Claude will call the appropriate sa_* tools automatically. No commands to memorize.
Frequently Asked Questions
What is the Syncific MCP server? +
The Syncific MCP server is a Model Context Protocol server that exposes Syncific's full publishing API as tools Claude can call. It includes 19 tools (all prefixed sa_) covering asset browsing, sync operations, destination management, AI enrichment, optimization, and platform administration.
How do I connect Syncific to Claude? +
In Claude.ai settings, go to Connectors and add a custom connector with your Syncific MCP server URL. The URL is available in your Syncific dashboard under Settings. Authentication uses your Syncific API key. Once connected, Claude can access all 19 Syncific tools in any conversation.
What can I do with the Syncific MCP server that I can't do in the dashboard? +
The MCP server enables natural language control of Syncific workflows, bulk operations described in plain English, and integration with other Claude capabilities — like combining Syncific publishing with Google Drive search, calendar scheduling, or Slack notifications in a single agentic workflow.
Is the Syncific MCP server included in all plans? +
The MCP server is included on all Syncific plans. All plans start with a 14-day free trial (credit card required). You also need a paid Claude plan (Pro or above) to use custom MCP connections in Claude.ai.
What are the sa_* tools in the Syncific MCP server? +
The 19 sa_ tools cover: sa_status (platform health), sa_activity (recent operations), sa_browse (source asset browsing), sa_sync (publish operations), sa_sync_map (source-to-destination mapping), sa_destinations (manage CMS connections), sa_groups (destination grouping), sa_enrichment (AI alt text and metadata), sa_generate (AI image generation), sa_optimize (compression reports), sa_intelligence (performance analytics), sa_actions (approve/reject recommendations), sa_settings, sa_team, sa_invites, sa_webhooks, sa_hub (multi-site), sa_autosync (scheduling), and sa_dest_test (connection testing).
Can I use the Syncific MCP server with Claude Code? +
Yes. Claude Code supports MCP connections. With Syncific connected in Claude Code, you can trigger asset publishing operations as part of development workflows — for example, automatically publishing optimized assets to a staging Contentful environment when a design review is approved.
Does Syncific support other AI assistants besides Claude via MCP? +
Syncific's MCP server implements the open Model Context Protocol standard and is compatible with any MCP client. As the MCP ecosystem grows, Syncific's tools will be accessible from any compliant AI assistant.
19 tools. Every CMS. Control everything through Claude.
No plugin required on destination sites. Cancel anytime.