The Agents section in your Skyp dashboard lets you connect Skyp to AI agents and external tools. The page is split into two tabs: Claude — for setting up Skyp as a custom connector in Claude — and Developers — for API keys, code snippets, and technical integrations. Skyp's MCP server also works with other OAuth-compatible clients including Cursor, Gemini, and Slack.
For platform-specific guides, see Using Skyp with Claude and Using Skyp with Slack.
Connecting Skyp to Claude (OAuth)
The Claude tab walks you through adding Skyp as a custom connector in Claude. This uses OAuth — no API key needed. Skyp handles authentication automatically when you authorize the connection.
Log in to your Skyp account and go to Agents in the left sidebar.
Click the Claude tab.
Open Claude Settings, navigate to MCP Servers, and click Add custom connector.
Fill in the following fields:
Name:Skyp
Remote MCP server URL:https://api.skyp.ai/mcpLeave Advanced settings (OAuth Client ID and Secret) empty — Skyp handles this automatically.
Click Add. A Skyp authorization page will open in a popup — review the requested permissions and click Allow. The popup will redirect to Claude's callback URL to complete the handshake, then close. Claude will now have access to your Skyp campaigns, contacts, and analytics.
You can copy the Name and MCP URL directly from the Claude tab using the copy icons next to each field. For a full Claude-specific guide, see Using Skyp with Claude.
Before creating a campaign via MCP or the API, make sure your company information is set up in Skyp (Company settings). Skyp requires a company profile to generate a campaign strategy and finalize a campaign. If no company is attached, the MCP tool will return an error asking you to add your company details first.
Connecting Cursor, Gemini, or Slack (OAuth)
Cursor, Gemini, and Slack all support connecting to Skyp via OAuth — no API key required. In each tool, add Skyp as a new MCP server using the URL https://api.skyp.ai/mcp, then complete the Skyp OAuth authorization when prompted.
Cursor: Go to Settings → MCP and click Add new MCP server.
Gemini: Add Skyp as an MCP extension from the Google AI Studio or Gemini extensions panel.
Slack: Add Skyp as an MCP server from your Slack workspace's AI integrations or app settings. For a full guide, see Using Skyp with Slack.
Refer to each tool's documentation for exact navigation steps, as UI placement may vary by version. The Skyp MCP URL and OAuth flow are the same regardless of which client you use.
Developers Tab
The Developers tab contains everything you need for custom integrations: API keys, a REST quick-start snippet, an MCP config block for tools that require manual configuration, and a downloadable SKILL.md agent guide. Use this tab if you're building a custom integration or connecting via a tool that requires an API key.
Generating an API Key
Go to Agents → Developers tab.
In the API Keys card, click Create API key.
Give your key a descriptive name (e.g. "Zapier integration", "Custom script").
Click Create.
Copy your key immediately — it's only shown once. Store it somewhere safe.
Once created, only the key prefix is visible. If you lose the key, revoke it and create a new one.
Managing Your API Keys
From the Agents → Developers tab you can:
Copy the key prefix to identify which key is which
Revoke a key by clicking the delete icon — this immediately disables it
See when a key was last used and when it was created
Using MCP Tools with Campaigns
When using Skyp's MCP tools (via Claude, Cursor, Gemini, Slack, or the API) to update campaigns, keep in mind that active, evergreen, and completed campaigns are locked — configuration changes will be rejected. To edit an active or evergreen campaign, go to Campaigns, pause it first, make your changes, then resume. Completed campaigns cannot be reopened.
CTAs are required before generating a strategy or finalizing. When building a campaign through the MCP flow, you must add at least one Call to Action (CTA) using create_new_cta before calling generate_campaign_strategy or finalize_campaign. If you attempt to proceed without a CTA, you'll receive an error prompting you to add one first. (The Skyp web UI enforces this automatically — this requirement also applies to the API and MCP flow.)