Bring Salsaengage
to VS Code Copilot
Learn how to connect Salsa Engage to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Salsa Engage MCP Server?
Connect your Salsa Engage account to any AI agent and take full control of your non-profit outreach and supporter orchestration through natural conversation. Salsa Engage provides a comprehensive platform for fundraising, advocacy, and marketing automation, and this integration allows you to retrieve supporter metadata, monitor engagement activities, and manage groups directly from your chat interface.
What you can do
- Supporter & Donor Orchestration — List all managed supporters and retrieve detailed profile metadata, including upserting contact records programmatically.
- Engagement Activity Intelligence — Access and monitor signatures, form submissions, and fundraising data to maintain a clear overview of campaign progress directly from the AI interface.
- Group & Segment Control — Manage supporter groups and assign contacts to targeted lists to ensure your communication is always synchronized via natural language.
- Operational Monitoring — Track system metrics, monitor webhooks, and retrieve account profile metadata using simple AI commands.
- Offline Donation Oversight — Access and list offline donation records to keep your financial and engagement data consistent.
How it works
1. Subscribe to this server
2. Enter your Salsa Engage API Token from your organization settings
3. Start managing your engagement workflows from Claude, Cursor, or any MCP-compatible client
No more manual report exports or group syncing. Your AI acts as a dedicated engagement coordinator or advocacy lead.
Who is this for?
- Non-profit Organizers — quickly retrieve supporter details and monitor petition counts without switching apps.
- Digital Marketers — automate the management of targeted groups and track activity metrics via natural conversation.
- Advocacy Teams — streamline the retrieval of engagement data and monitor campaign health directly within the chat.
Built-in capabilities (12)
Add supporters to a group
Verify Salsa Engage API connectivity
Get authenticated account details
Retrieve performance metrics
List active webhooks
Search and list activities
List offline donation records
Search and list groups
List defined segments
Search and list supporters
Create or update a group
Create or update a supporter
Why VS Code Copilot?
GitHub Copilot Agent mode brings Salsa Engage data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Salsa Engage in VS Code Copilot
Salsa Engage and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Salsa Engage to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Salsa Engage in VS Code Copilot
The Salsa Engage MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Salsa Engage for VS Code Copilot
Every tool call from VS Code Copilot to the Salsa Engage MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find all supporters who signed a specific petition today?
Yes! Use the list_engagement_activities tool with a date filter. Your agent will respond with the complete metadata for all participants and their submission details in seconds.
How do I find my Salsa Engage API Token?
Log in to your Salsa Engage account, navigate to Organization Settings > API tab, and you will find your unique Integration API token listed there.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.