Salesforce Marketing

io.github.ZLeventerPublished by GitHub account ZLeventerv1.0.1Updated Oct 30, 2026

MCP server for Salesforce — 47 tools for leads, campaigns, pipeline, attribution, and reporting.

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Local MCP server that connects an assistant to Salesforce, exposing 47 tools for leads, campaigns, pipeline, attribution and reporting.

What you can do
  • Work with leads and campaigns in a Salesforce org
  • Inspect pipeline and attribution data
  • Produce reports from Salesforce records
  • Use a configurable REST API version and login URL, including sandbox orgs
When to use it
Useful when an assistant needs to read or work with Salesforce marketing and sales data — leads, campaigns, pipeline, attribution and reports — from a desktop MCP client, including against a sandbox org.
Requirements
Runs as a local npm package over stdio on a desktop machine. Needs a Salesforce account with the login email (SF_USERNAME), password (SF_PASSWORD) and security token (SF_SECURITY_TOKEN); optionally SF_LOGIN_URL for sandbox and SF_API_VERSION. Network access to Salesforce is required.
Before you install
Requires the Salesforce password and security token as environment variables, which grant account access; store them carefully. The tool list is not published, so which operations read versus write or delete records is unclear — verify before letting an assistant change data. Pointing SF_LOGIN_URL at a sandbox is advisable for testing.

Installation

In SourceWeft

  1. Open Salesforce Marketing in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.