SlideCold MCP server
Commit Nov 2, 2026Enables AI agents to manage Instagram cold-DM outreach campaigns, audiences, conversations, and proxy settings via the SlideCold API.
Also known as slidecold/slidecold-mcp
- Stars
- 0
- Tools
- 3
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 2, 2026
- License
- MIT
What is SlideCold MCP?
SlideCold enables AI agents to manage Instagram cold-DM outreach campaigns, audiences, conversations, and proxy settings via the SlideCold API. It exposes 3 tools, such as readOnlyHint, destructiveHint, idempotentHint.
Summary generated from the project's README
About SlideCold MCP server
Managing Instagram cold-DM outreach campaigns through an AI assistant is what this server enables. It provides access to all 49 SlideCold API operations, allowing users to control audiences, conversations, accounts, and proxy settings directly from MCP clients like Claude, Cursor, or Windsurf. The server operates over stdio and requires a SlideCold API key starting with the cs_ prefix.
Users can organize their outreach by managing campaigns, scraping or importing audience members, and handling direct messages. The toolset includes specific functions for sending replies or photos, checking account proxy health, and managing account warmup status. To ensure safety, the server uses annotations to signal which actions are read-only, idempotent, or destructive, such as sending a message to a real person or deleting a campaign.
Setup involves configuring the SLIDECOLD_API_KEY environment variable. Developers can restrict the assistant's capabilities by using scoped API keys, such as a read-only key with the *:read scope, to prevent unauthorized modifications to accounts or campaigns.
Written from the project's README. Every use case is checked against a quote from it.
SlideCold MCP tools 3
Detected from the READMEreadOnlyHintdestructiveHintidempotentHint
Configuration
SLIDECOLD_API_KEY
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableslidecold/slidecold-mcp is public and reachablegithub.com/slidecold/slidecold-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-02github.com/slidecold/slidecold-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubslidecold-mcp
Official MCP server for SlideCold (Instagram cold-DM outreach). It gives Claude, Cursor and any other MCP client all 49 SlideCold API operations as tools, over stdio. Built on the slidecold Node.js SDK. Node.js 18 or newer.
Create an API key (cs_...) at https://slidecold.com/settings. Give the server only the scopes you want the assistant to have; a read-only key (*:read) is a good start.
Setup
Claude Code
claude mcp add slidecold -e SLIDECOLD_API_KEY=cs_... -- npx -y slidecold-mcp
Claude Desktop (Settings > Developer > Edit Config, claude_desktop_config.json)
{
"mcpServers": {
"slidecold": {
"command": "npx",
"args": ["-y", "slidecold-mcp"],
"env": { "SLIDECOLD_API_KEY": "cs_..." }
}
}
}
Cursor (~/.cursor/mcp.json, or .cursor/mcp.json in a project): the same mcpServers JSON as Claude Desktop.
Other clients (Windsurf, VS Code, Cline, Zed, ...): register a stdio server with command npx, arguments -y slidecold-mcp and the environment variable SLIDECOLD_API_KEY. With a global install (npm install -g slidecold-mcp) the command is just slidecold-mcp.
Configuration
| Setting | Source |
|---|---|
| API key | SLIDECOLD_API_KEY, then apiKey in the config file |
| API URL | SLIDECOLD_BASE_URL, then baseUrl in the config file, then https://slidecold.com/api/v1 |
The config file is written by slidecold login from the SlideCold CLI: $XDG_CONFIG_HOME/slidecold/config.json (default ~/.config/slidecold/config.json), or %APPDATA%\slidecold\config.json on Windows. If you have logged in with the CLI you can leave out SLIDECOLD_API_KEY.
{ "apiKey": "cs_...", "baseUrl": "https://slidecold.com/api/v1" }
Tools
One tool per API operation, named after its operationId in snake case. Each description gives the summary, the required API key scope and the HTTP endpoint.
| Group | Tools |
|---|---|
| Campaigns (8) | list_campaigns, create_campaign, get_campaign, update_campaign, delete_campaign, get_campaign_stats, list_campaign_recipients, retry_campaign |
| Audiences (10) | list_audiences, create_audience, get_audience, update_audience, delete_audience, list_audience_members, import_audience_members, export_audience, start_audience_scrape, stop_audience_scrape |
| Conversations (8) | list_conversations, refresh_conversations, get_conversation, update_conversation, send_conversation_reply, send_conversation_photo, export_conversation_lead, delete_conversation_message |
| Accounts (14) | list_accounts, create_account, get_login_status, get_accounts_proxy_health, verify_account_2fa, verify_account_challenge, get_account, update_account, delete_account, check_account_session, relogin_account, set_account_listening, get_account_warmup_history, get_account_warmup_status |
| Proxies (5) | list_proxies, create_proxy, update_proxy, delete_proxy, test_proxy |
| Folders (4) | list_folders, create_folder, update_folder, delete_folder |
Arguments are the path parameters (e.g. id), the query parameters, and body for the JSON request body. Upload tools (send_conversation_photo, import_audience_members) take a local file_path. API errors come back as tool errors carrying the API's message, e.g. SlideCold API error 404: Campaign not found.
Annotations
Every tool carries MCP annotations so clients can ask before risky calls:
readOnlyHint: trueon every GET tool (list_*,get_*,export_audience).destructiveHint: trueon every DELETE tool (delete_*,stop_audience_scrape) and on the two tools that send a DM to a real person and cannot be undone:send_conversation_replyandsend_conversation_photo. Other write tools havedestructiveHint: false.idempotentHint: trueon GET, PUT, PATCH and DELETE tools.
Scopes
Each API key carries scopes <resource>:<read|write> for accounts, audiences, campaigns and conversations; :write also grants :read. Proxy tools use the accounts scopes; folder tools use the scope of the folder's type. Read tools need :read, everything else needs :write. A tool called without the scope returns a 403 tool error such as This API key is missing the campaigns:write scope.
MCP Registry
server.json describes this server for the official MCP Registry as io.github.slidecold/slidecold-mcp; the matching mcpName in package.json proves ownership of the npm package. After a version is on npm, publish it to the registry with mcp-publisher:
mcp-publisher login github # as a member of the slidecold GitHub org
mcp-publisher publish
Bump version in server.json (top level and in packages) together with package.json; the release workflow checks they match the tag.
Development
npm install
npm run build
npm run typecheck
npm test
The tests start the built stdio server (dist/bin.js), list its 49 tools and call them against a local mock API.
To develop against an unreleased SDK, build it in a sibling checkout of slidecold-node and link it without touching package.json:
(cd ../slidecold-node && npm install && npm run build)
npm install --no-save ../slidecold-node # node_modules/slidecold -> ../slidecold-node
Releases are cut by bumping the versions in package.json and server.json, adding a CHANGELOG entry and pushing a matching vX.Y.Z tag; CI tests, publishes to npm with provenance and creates the GitHub release.
License
MIT
SlideCold MCP questions
What tools does SlideCold MCP provide?
It exposes 3 tools, including readOnlyHint, destructiveHint, idempotentHint.
What kind of tools are available in this server?
The server provides 49 tools organized into groups including Campaigns, Audiences, Conversations, Accounts, Proxies, and Folders.
Can I limit the permissions of the AI assistant?
Yes, you can create an API key with specific scopes; for example, a read-only key (*:read) is recommended for starting.
Does the server support file uploads?
Yes, tools like send_conversation_photo and import_audience_members accept a local file path for uploads.