Introduction to MCP
One Stacksync MCP connection to manage your platform and access external systems through MCP Gateway
Stacksync connects your AI assistant to two capabilities through one MCP server: Stacksync MCP for managing the Stacksync platform, and Stacksync MCP Gateway for working in external systems through a controlled layer.
Connect Stacksync once in your AI assistant. That same connection gives you access to both capabilities, subject to your permissions and workspace settings. You do not need a separate gateway connection.
What is MCP?
The Model Context Protocol (MCP) is a way for AI assistants to discover and use tools provided by a service. With Stacksync, it lets your assistant turn a request in plain language into actions on your platform resources or connected apps.
Stacksync MCP and MCP Gateway
| Stacksync MCP | Stacksync MCP Gateway | |
|---|---|---|
| Purpose | Configure and operate the Stacksync platform | Access and act on external systems through Stacksync |
| What it works with | Stacksync resources: connections, syncs, workflows, Genies and more | Connected apps: CRMs, ERPs, databases and other systems |
| Example request | "Create a two-way sync between Salesforce and PostgreSQL." | "Find the Acme account in Salesforce and update its phone number." |
| Access controls | Your Stacksync workspace role and workspace governance settings | Your permissions, MCP Gateway Policies, app guardrails and workspace governance settings |
| Connection | The same Stacksync MCP server | The same Stacksync MCP server |
Manage the Stacksync platform
Use Stacksync MCP to create and configure resources, run workflows, start or pause syncs, and investigate issues. Your assistant operates on your behalf with your Stacksync permissions.
Explore Stacksync platform management.
Work in external systems through MCP Gateway
An MCP gateway sits between an AI assistant and the systems it accesses. Stacksync MCP Gateway uses your workspace's existing app connections to let your assistant search, read, create and update data directly. Workspace owners control access, set custom guardrails and monitor activity in Stacksync.
For example, creating a sync is a Stacksync platform operation. Updating a Salesforce record directly is a gateway action. Both requests go through the same MCP connection.
Explore Stacksync MCP Gateway.
Connect once
Add this server URL to your AI assistant:
https://mcp.stacksync.com/mcpIn the Stacksync app, open MCP → Connect to copy the URL and find setup instructions. After connecting and signing in, ask: "List my Stacksync workspaces."
Connect your AI assistant has instructions for supported clients.
Authentication
Sign in with your Stacksync login using OAuth and choose a default workspace. Your assistant acts on your behalf, with your role in each workspace. You can grant read-only access by clearing Make changes during sign-in.
The same sign-in covers platform management and gateway access. For scripts, CI pipelines and clients without OAuth, use an API key. You can review and revoke signed-in assistants from the Sessions tab of the MCP page.
Learn about authentication, sessions and API keys.
MCP Gateway Policies
Policies decide which external apps and actions members' assistants can use directly. Every workspace has a Default Policy. Owners can create custom policies for users and groups and add app-specific guardrails in plain language. When several policies apply to a member, every one is evaluated and the most permissive verdict sets the outcome.
Policies govern direct app access. Stacksync resources such as workflows, Genies and syncs continue to follow workspace roles.
Configure MCP Gateway Policies.
MCP Activity Log
The Activity Log brings platform and gateway activity together: who made a call, through which assistant, what it acted on and how it ended. Use it to monitor successful calls, blocked actions, approval requests and errors. Owners see workspace activity; other members see their own.
Governance and security
Workspace owners can turn on Ask before every change to require approval for changes and control whether assistants can read troubleshooting logs. Workspace roles, gateway policies and guardrails work together to control access. App credentials stay in Stacksync.
Review governance and security.