Connect Syft to Your AI Agent
Syft exposes an MCP (Model Context Protocol) server that lets AI assistants query your visitor data, enqueue leads into motions, and build automations.
The Syft MCP server is available exclusively on Pro plans. Upgrade your plan to get started.
What you need
- A Syft workspace on the Pro plan.
- The Syft MCP server URL:
https://app.syftdata.com/api/mcp - One of two ways to sign in:
- Sign in with Syft (OAuth). Your assistant opens a Syft login window. No key to copy. This is the easiest option and works in Claude, ChatGPT, Microsoft Copilot Studio and most coding agents.
- API key. Paste your workspace's secret API key into the assistant's settings. Use this when an assistant has no sign-in option.
Many companies switch off custom connectors until IT approves them. If you can't find the option to add one, or you see an error like "not allowed by your organization", send your admin the request message below.
Chat assistants
These are the assistants most marketing and sales teams use day to day.
- Claude & Cowork
- ChatGPT
- Microsoft Copilot
- Gemini
Works in Claude on the web, the desktop app, and Claude Cowork. Cowork uses the same connectors as the rest of Claude, so you only set this up once.
Pro and Max plans
- In Claude, go to Customize > Connectors, click + Add, then Add custom connector.
- Name it
Syftand paste the server URL:https://app.syftdata.com/api/mcp - Click Continue, keep the detected sign-in settings, and click Add.
- A Syft login window opens. Sign in with the email you use for Syft.
- In any chat, click + > Connectors and make sure Syft is switched on.
Team and Enterprise plans
Only an Owner (or a role with connector permissions) can add a custom connector:
- The Owner goes to Organization settings > Connectors > Add > Custom > Web and adds the server URL above.
- Each member then goes to Customize > Connectors, finds Syft (labeled Custom), and clicks Connect to sign in with their own Syft account.
ChatGPT connects with Sign in with Syft only. It does not accept API keys.
Business, Enterprise and Edu workspaces
Only workspace admins and owners can add custom MCP servers:
- An admin enables Developer mode for the workspace, then creates a new app (or plugin) for a custom MCP server.
- Set the Name to
Syftand the MCP Server URL to:https://app.syftdata.com/api/mcp - Choose OAuth for authentication, leave the other settings as defaults, and create it.
- Publish it to the workspace.
- Each member opens a chat, enables Syft, and completes the Syft sign-in when prompted.
Plus and Pro accounts
Go to Settings > Apps (called Plugins in some accounts), turn on Developer mode if asked, and add a custom MCP server with the URL above and OAuth sign-in.
OpenAI is renaming this area from "Connectors" to "Apps" to "Plugins", so labels in your account may differ slightly. Look for an option to add a custom MCP server.
Use Microsoft Copilot Studio to add Syft as a tool to an agent, then publish that agent to Microsoft 365 Copilot and Teams.
- In Copilot Studio, open your agent (or create one) and go to Tools > Add a tool > New tool > Model Context Protocol.
- Fill in:
- Server name:
Syft - Server description:
Syft website visitor, account, and lead data - Server URL:
https://app.syftdata.com/api/mcp
- Server name:
- Choose an Authentication type:
- OAuth 2.0 > Dynamic discovery (recommended). Each user signs in with their own Syft account.
- API key > Header, with header name
Authorizationand valueBearer <your-syft-api-key>. Everyone using the agent shares your workspace's key.
- Click Create, then Create a new connection, sign in, and click Add to agent.
- To use it in Microsoft 365 Copilot and Teams, Publish the agent, then go to Channels > Teams and Microsoft Copilot, keep Make agent available in Microsoft Copilot checked, and click Add channel.
Copilot Studio routes MCP servers through Power Platform connectors. If the tool is blocked, your Power Platform admin needs to allow it in the data (DLP) policy. Sharing the agent with your whole organization also needs admin approval in the Teams admin center. See For admins.
Developers building a declarative agent with the Microsoft 365 Agents Toolkit can also add Syft through Add an Action > Start with an MCP Server, using the same URL.
Gemini app (personal Google accounts)
- Open gemini.google.com and go to Settings > Connected Apps.
- Click Add a custom app and enter:
https://app.syftdata.com/api/mcp - Sign in with your Syft account when prompted.
Google currently limits custom apps to personal accounts in supported regions. Work and school accounts can't add them yet.
Gemini Enterprise and Google Workspace
Gemini Enterprise only accepts MCP servers with a manually registered OAuth client, and Gemini in Workspace doesn't support custom MCP servers. Contact us if you need Syft in Gemini Enterprise. Technical users can connect through Gemini CLI today.
Coding agents
For RevOps, growth engineers, and anyone working from an IDE or terminal.
- Claude Code
- VS Code + GitHub Copilot
- Cursor
- Windsurf
- OpenAI Codex
- Gemini CLI
- Other clients
-
Add the Syft MCP server from your terminal:
claude mcp add syft --transport http https://app.syftdata.com/api/mcp -
Start Claude Code and run:
/mcp -
A browser window opens asking you to authenticate with Syft. Sign in and approve access.
Once approved, syft appears in /mcp along with its tools (query_entities, lookup_entities, build_motion, etc.) and is ready to use.
To use an API key instead of signing in, add --header "Authorization: Bearer <your-syft-api-key>" to the claude mcp add command.
Works with GitHub Copilot in agent mode.
-
Open the Command Palette and run MCP: Add Server, choose HTTP, and enter the server URL. Or create
.vscode/mcp.jsonin your project:{
"inputs": [
{
"type": "promptString",
"id": "syft-key",
"description": "Syft API key",
"password": true
}
],
"servers": {
"syft": {
"type": "http",
"url": "https://app.syftdata.com/api/mcp",
"headers": {
"Authorization": "Bearer ${input:syft-key}"
}
}
}
} -
Click Start above the
syftentry. VS Code asks for your API key once and stores it securely. -
In Copilot Chat, switch to Agent mode and open the tools picker to check that the Syft tools are enabled.
VS Code uses a top-level "servers" key, not "mcpServers". Using the wrong key is the most common reason the server doesn't show up.
Copilot coding agent on github.com
In your repository, go to Settings > Copilot > MCP servers and add:
{
"mcpServers": {
"syft": {
"type": "http",
"url": "https://app.syftdata.com/api/mcp",
"tools": ["*"],
"headers": {
"Authorization": "Bearer $COPILOT_MCP_SYFT_KEY"
}
}
}
}
Then add a repository secret named COPILOT_MCP_SYFT_KEY in the copilot environment containing your API key. The coding agent doesn't support OAuth sign-in, so an API key is required.
Go to Settings > MCP > Add new global MCP server (or edit ~/.cursor/mcp.json) and add:
{
"mcpServers": {
"syft": {
"url": "https://app.syftdata.com/api/mcp",
"headers": {
"Authorization": "Bearer <your-syft-api-key>"
}
}
}
}
Replace <your-syft-api-key> with your API key. To sign in with Syft instead, leave out the headers block; Cursor then prompts you to sign in from its MCP settings.
Add the following to ~/.codeium/windsurf/mcp_config.json (or the MCP settings in Windsurf / Devin Desktop):
{
"mcpServers": {
"syft": {
"serverUrl": "https://app.syftdata.com/api/mcp",
"headers": {
"Authorization": "Bearer <your-syft-api-key>"
}
}
}
}
Windsurf uses serverUrl, not url. Replace <your-syft-api-key> with your API key, then refresh the MCP server list.
-
Add the server:
codex mcp add syft --url https://app.syftdata.com/api/mcp -
Sign in with Syft:
codex mcp login syft
To use an API key instead, edit ~/.codex/config.toml:
[mcp_servers.syft]
url = "https://app.syftdata.com/api/mcp"
bearer_token_env_var = "SYFT_API_KEY"
and set the SYFT_API_KEY environment variable to your API key.
-
Add the server:
gemini mcp add --transport http syft https://app.syftdata.com/api/mcp -
Start Gemini CLI and sign in with Syft:
/mcp auth syft
Or edit ~/.gemini/settings.json directly. Use httpUrl (not url, which means SSE):
{
"mcpServers": {
"syft": {
"httpUrl": "https://app.syftdata.com/api/mcp",
"headers": {
"Authorization": "Bearer <your-syft-api-key>"
}
}
}
}
The same steps work in Antigravity CLI.
Any MCP client that supports remote servers can connect:
| Setting | Value |
|---|---|
| URL | https://app.syftdata.com/api/mcp |
| Transport | Streamable HTTP (SSE is not supported) |
| Auth option 1 | OAuth 2.1 with discovery and dynamic client registration |
| Auth option 2 | Header Authorization: Bearer <your-syft-api-key> |
If your client only runs local (stdio) servers, bridge it with mcp-remote:
{
"mcpServers": {
"syft": {
"command": "npx",
"args": [
"mcp-remote",
"https://app.syftdata.com/api/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <your-syft-api-key>"
}
}
}
}
Check that it works
Paste this into a new chat:
You: Use Syft to show my org setup.
Your assistant should call Get Org Setup and list your ICPs, personas, signals and motions. If it does, you're connected. If not, see Troubleshooting & FAQ.
Available Tools
Once connected, your AI agent can use the following Syft tools. They're grouped by what they help you do — most agents will pick the right one automatically based on your request.
Discover & research
| Tool | Description |
|---|---|
| Query Entities | Natural-language search across your accounts and contacts. "Find SaaS companies in the US who visited our pricing page." Supports sorting/ranking, e.g. "top 50 accounts by sessions." |
| Lookup Entities | Deterministic lookup of specific contacts by email or companies by domain — returns their site activity, session history, and intent signals. |
| Find Connections | Surface warm intros from your team's LinkedIn network. "Do we know anyone at Acme?" Searches connections synced via the Syft extension. |
Configure your GTM setup
| Tool | Description |
|---|---|
| Get Org Setup | View your ICPs, personas, signals, motions, connected integrations, and available filter fields. |
| Build ICP | Create or edit an Ideal Customer Profile (company-level targeting) through a guided, multi-turn conversation. |
| Build Persona | Create or edit a Persona (contact-level targeting: role, seniority, function) conversationally. |
| Build Signal | Create or edit a behavioral Signal to watch for — pricing-page visits, demo requests, UTM params, LinkedIn engagement, etc. |
| Create Target List | Build a Target Account List (TAL) — a target, do-not-track, or competitor list of accounts/contacts. |
| Delete Entity | Delete an ICP, Persona, or Signal. Refuses with a clear error if the entity is still referenced by a motion or list, so you never break a live filter. |
Run & automate
| Tool | Description |
|---|---|
| Build Motion | Create or edit an automation workflow (trigger → filters → actions) through a conversational, multi-turn flow. |
| Enqueue Leads | Push a list of leads into an active motion for outreach (LinkedIn, CRM sync, email campaigns, etc.). |
| Get Motion Runs | Review motion runs — pending approvals, in-progress, completed, or failed — with action plans and step details. |
| Manage Motion Run | Approve, reject, or modify a motion run that's waiting for approval (edit message copy or drop steps before it executes). |
Setup & admin
| Tool | Description |
|---|---|
| Get Web Tag Snippet | Generate the Syft tracking-tag install snippet and steps for your platform (HTML, GTM, Next.js, Webflow, Framer, WordPress, Mintlify, Docusaurus, GitBook). |
| Verify Tag Installation | Confirm the Syft tag is installed and firing for your org. |
| Send Tag Setup Email | Email platform-specific install instructions to a teammate (e.g. the developer who manages your site). |
| Invite User to Workspace | Send an email invitation for a teammate to join your Syft workspace. |
| Get Billing Info | Check your credit usage, plan details, and billing history. |
See Example Scenarios for step-by-step walkthroughs of what you can do with these tools.
For admins
If your company manages AI tools centrally, someone with admin rights has to allow Syft before members can connect. Here is where that setting lives in each product:
| Product | What the admin needs to do |
|---|---|
| Claude Team / Enterprise | An Owner adds Syft under Organization settings > Connectors > Add > Custom > Web. Members can't add custom connectors themselves. |
| ChatGPT Business / Enterprise / Edu | An admin creates the Syft app (custom MCP server) and publishes it to the workspace. On Enterprise and Edu, admins can also grant members permission to create apps. |
| Microsoft Copilot Studio / M365 Copilot | Allow the MCP connector in the Power Platform data (DLP) policy for the environment. To share the agent org-wide, approve it in the Teams admin center. Power Platform apps must be allowed in Teams. |
| GitHub Copilot Business / Enterprise | Turn on the MCP servers in Copilot policy (Enterprise AI controls or Organization > Copilot > Policies). If Restrict MCP access to registry servers is set to Registry only, add Syft to your MCP registry. |
| VS Code (managed) | If your organization deploys VS Code policies that restrict MCP servers, add https://app.syftdata.com/api/mcp to the allowed list. |
| Cursor Teams | Add Syft to the MCP Allowlist in Team Settings > MCP Configuration. |
| Windsurf Teams | Add Syft to the MCP allowlist in team settings. The server ID must match the config key (syft). Once any server is allowlisted, all others are blocked. |
| Claude Code (managed) | Add {"serverUrl": "https://app.syftdata.com/*"} to allowedMcpServers in managed settings. |
| Network / proxy / firewall | Allow HTTPS to app.syftdata.com. For sign-in, also allow syft-studio.us.auth0.com. |
Message for your IT admin
Copy this, fill in the bracketed parts, and send it to whoever manages your AI tools:
Hi [name],
I'd like to connect Syft (our website visitor and lead intelligence tool) to
[Claude / ChatGPT / Microsoft Copilot / other] so I can ask it about our
accounts and leads from chat.
Syft provides a remote MCP server:
URL: https://app.syftdata.com/api/mcp
Transport: Streamable HTTP
Sign-in: OAuth (each user signs in with their own Syft account)
Could you allow this server for our workspace? Setup steps for each
assistant, including the admin settings, are here:
https://docs.syftdata.com/ai-agents/connect#for-admins
Syft's security and data processing details: https://www.syftdata.com/dpa
Thanks!
Troubleshooting & FAQ
Search this page for the exact error message you see. Most problems fall into one of these.
I can't find "Add custom connector", or it says "not allowed by your organization"
Your admin has switched off custom connectors or MCP servers for your workspace. On Claude Team and Enterprise, and on ChatGPT Business and Enterprise, only admins can add them. Send your admin the request message, and point them to For admins.
"the MCP server requires a Syft Pro plan"
The full message reads: "could not connect to Syft: the MCP server requires a Syft Pro plan and this workspace is on ... Your credentials are valid, so reconnecting will not help."
Your sign-in worked, but your workspace isn't on Pro. Reconnecting won't fix it. Upgrade to Pro, then reconnect.
"is not a member of any Syft workspace"
You signed in with an email address that isn't part of a Syft workspace. The error shows which address was used. This usually happens when your browser is logged in to a personal Google account instead of your work one.
Disconnect Syft in your assistant, sign out of the other account (or use a private window), and reconnect with the email you use for Syft. If you're new to the team, ask a teammate to invite you to your company's Syft workspace first.
"this workspace is no longer active"
The workspace's subscription has lapsed. A workspace admin can reactivate it from Billing.
401 Unauthorized, "invalid_token", or "No authorization provided"
Syft didn't receive a valid key or sign-in. Check that:
- The header value is
Bearer(with a space) followed by the key. - You copied the full secret API key (it starts with
sk_), not the public tracking snippet ID. - The key hasn't been rotated. Rotating invalidates the old key immediately.
- If you used Sign in with Syft, your session may have expired. Disconnect and reconnect.
The sign-in window closes, loops, or shows a redirect error
- Allow pop-ups for your assistant's site, then try again.
- Make sure you're signing in with your Syft email (see above).
- Desktop and IDE apps open your default browser for sign-in. If that browser is a different profile, finish sign-in there, or switch to the API key method if your client supports it.
Connected, but no Syft tools show up
- Turn the connector on for this chat. In Claude, use + > Connectors. In ChatGPT, enable Syft from the composer. In VS Code and Cursor, check the tools picker.
- Restart the app or reload the MCP server list after editing a config file.
- Check the config key. VS Code uses
servers, while most other clients usemcpServers. Windsurf usesserverUrl, and Gemini CLI useshttpUrl. - Check the JSON. A trailing comma or a missing brace stops the whole file from loading.
"SSE error", "405 Method Not Allowed", or the connection hangs
Your client is trying to connect over SSE (server-sent events). Syft only supports Streamable HTTP. Set the transport to http / Streamable HTTP. In Gemini CLI, use httpUrl instead of url. If your client can't do Streamable HTTP, use the mcp-remote bridge under Other clients.
The assistant answers without using Syft
Assistants decide when to call tools, and sometimes they answer from general knowledge instead. Mention Syft in your request ("Use Syft to find...") and make sure the connector is switched on for the current chat.
Tools work, but return no visitors or accounts
The Syft tracking tag probably isn't installed or isn't firing on your site. Ask your assistant to "verify my Syft tag installation", or follow the Quick Start.
It fails on the office network or VPN but works elsewhere
A proxy or firewall is blocking the connection. Ask IT to allow HTTPS to app.syftdata.com and syft-studio.us.auth0.com (see For admins).
What can the assistant see and do?
The assistant acts with your access to your Syft workspace. It can read accounts, contacts and activity, and it can change things like ICPs, signals, motions and motion runs. Most assistants ask you to approve each tool call that makes a change. You can usually set tools to always require approval in the assistant's settings.
How do I disconnect or revoke access?
Remove or disconnect Syft from the assistant's connector or MCP settings. If you used an API key and think it may have been exposed, rotate it. Rotating cuts off every client using the old key.
Which plans include MCP access?
Only Pro. Trial workspaces include Pro features, so MCP works during a trial too. See Credits & Usage.
Still stuck?
Email support@syftdata.com with:
- The assistant you're using (for example Claude Team or VS Code + Copilot).
- The exact error text, or a screenshot.
- The email address you signed in with.