Campaignstack

io.campaignstackPublished by campaignstack.ioOfficial publisherv0.1.0Updated Oct 28, 2026

Run B2B outreach from your AI agent: 250+ tools for campaigns, leads, LinkedIn and email workflows.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an AI assistant run B2B outreach campaigns, leads, LinkedIn and email workflows through Campaignstack's 250+ tools.

What you can do
  • Manage outreach campaigns and their sequences
  • Work with leads and prospect data
  • Run LinkedIn and email outreach workflows
  • Operate Campaignstack from an AI agent through a broad tool set (250+ tools)
When to use it
Useful when you want an assistant to help build and operate B2B outreach — campaigns, lead lists, and LinkedIn or email sequences — inside a Campaignstack workspace instead of clicking through the dashboard.
Requirements
Remote streamable HTTP endpoint at mcp.campaignstack.io with OAuth authentication; an Authorization bearer token using a Campaignstack API key (workspace or user key) created in the dashboard under Settings. No local runtime or packages needed.
Before you install
The server requires a Campaignstack API key sent as an Authorization bearer token; treat it as a secret. Outreach tools can act on real prospects and send LinkedIn or email messages, so review before letting an assistant run campaigns or contact people. Tool list is not published in the manifest, so confirm scope in the dashboard.

Installation

In SourceWeft

  1. Open Campaignstack in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.campaignstack%2Fcampaignstack/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "campaignstack": {
      "type": "http",
      "url": "https://mcp.campaignstack.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.