能做什么
Drive a GetSales workspace: tables, people, companies, enrichment, workflows, inbox, tasks, signals.
作者提供的原文
- 连接方式 电脑或云端
- 账号或密钥 云端:连接时登录该服务(OAuth) · 本地:需要 GETSALES_API_KEY
- 分类 营销与社交媒体
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
为什么排在这里
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-08 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 GetSales: Outreach MCP Server。按照 https://mcp.popnx.com/i/getsales-outreach-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp2.getsales.io) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称GetSales: Outreach MCP ServerRemote MCP server URL · 地址https://mcp2.getsales.io/mcp/public在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsGetSales: Outreach MCP Server
试一试
用 GetSales: Outreach MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 GetSales: Outreach MCP Server,或回答中出现 GetSales: Outreach MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称GetSales: Outreach MCP ServerConnection · 地址https://mcp2.getsales.io/mcp/public在聊天中选择 GetSales: Outreach MCP Server
开启新聊天,输入前先从插件列表中选择 GetSales: Outreach MCP Server
试一试
用 GetSales: Outreach MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 GetSales: Outreach MCP Server,或回答中出现 GetSales: Outreach MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user outreach https://mcp2.getsales.io/mcp/public在 Claude Code 中输入 /mcp
应能看到 GetSales: Outreach MCP Server 在列表中并显示已连接
试一试
用 GetSales: Outreach MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 GetSales: Outreach MCP Server,或回答中出现 GetSales: Outreach MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 GetSales: Outreach MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 GetSales: Outreach MCP Server,或回答中出现 GetSales: Outreach MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 GetSales: Outreach MCP Server 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 GetSales: Outreach MCP Server,或回答中出现 GetSales: Outreach MCP Server 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp2.getsales.io/mcp/publicJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user outreach https://mcp2.getsales.io/mcp/publicCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"outreach": {
"url": "https://mcp2.getsales.io/mcp/public"
}
}
}VS Code (mcp.json)
{
"servers": {
"outreach": {
"type": "http",
"url": "https://mcp2.getsales.io/mcp/public"
}
}
}安装在电脑上
Claude Code
claude mcp add --scope user outreach --env GETSALES_API_KEY=your-value -- npx -y @getsales/outreach-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"outreach": {
"command": "npx",
"args": [
"-y",
"@getsales/outreach-mcp"
],
"env": {
"GETSALES_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"outreach": {
"command": "npx",
"args": [
"-y",
"@getsales/outreach-mcp"
],
"env": {
"GETSALES_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"outreach": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@getsales/outreach-mcp"
],
"env": {
"GETSALES_API_KEY": "your-value"
}
}
}
}需要你填写的值
GETSALES_MCP_URLenv端点覆盖项。默认为 https://mcp2.getsales.io/mcp/public查看英文原文
Endpoint override. Defaults to https://mcp2.getsales.io/mcp/public.GETSALES_API_KEY机密 必填 envA gs_live_... API key from the app (Settings, API keys), sent as the bearer on every call. Unset, the launcher signs in with OAuth on first use instead, so no credential goes in the client config.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 getsales.io 验证(注册中心会核实域名所有权)
- ✓ 通过
仍在维护
代码最后更新于6天前
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 386 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
已公开的漏洞(OSV.dev)
OSV.dev 中没有 @getsales/outreach-mcp@1.0.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/getsales-outreach-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 4261 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 4261 个服务器的 73% 更新
- 基础检查结果等于或优于此分类中其他 4261 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
GetSales: Outreach MCP Server 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:GETSALES_API_KEY
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于6天前,最新版本(1.0.0)于12天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Relaticle
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
ChatbotX
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
X (Twitter) MCP Server by Xquik
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Betterlytics
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
BibiGPT YouTube Video Summarizer
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| 本项 GetSales: Outreach MCP Server | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 是 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
GetSales: Outreach MCP Server
GetSales is LinkedIn and email outreach for agencies and GTM teams, in one app. Describe who you sell to, and GetSales finds the people and their work emails, scores them and writes the first lines, and every reply comes back to a team inbox.
This MCP server lets an AI agent work in your GetSales workspace. Claude, Cursor, ChatGPT or another MCP client connects to one hosted endpoint, https://mcp2.getsales.io/mcp/public, and through four meta-tools reaches the tables of people and companies, the enrichment columns, the workflows, the inbox with the AI SDR's drafts, the tasks, the website signals and the webhooks.
The server runs hosted, so this repository holds its kit and no server code: client configs for the URL, npx and Docker setups, the npm launcher and its image, the MCP Registry entry, the Claude Code and Cursor plugin manifests and an agent skill.
What is an outreach MCP server?
An outreach MCP server puts the objects of an outreach product behind Model Context Protocol tools, so an AI agent can do from a chat what a person does in the app: build a list of the right people, enrich it, put it into a sequence and keep up with the replies. MCP is the open protocol that Claude, Cursor, ChatGPT and other clients use to call tools on a server.
This one works on the objects of your own GetSales workspace. Ask for a table built from one sentence, a work email column priced before it runs, a workflow drafted for the people who qualify, or the threads that wait for you, and the agent chains the calls. The tools the server marks dangerous, such as the delete and cancel tools, show a preview and run only after you confirm. Paid work is not behind that preview, so the skill in this repository has the agent quote the estimate and wait for your yes before it starts any.
Which clients does it work with?
Any MCP client that speaks streamable HTTP or can start a command:
- Claude: claude.ai, Claude Desktop and Claude Code
- Cursor
- ChatGPT, through custom connectors
- VS Code, Codex and other agent runtimes
Not on MCP? Each tool maps to an endpoint of the GetSales REST API, documented at docs.getsales.io, and one API key works on both.
How do I connect GetSales to Claude, Cursor or ChatGPT?
| Setup | For | Sign-in | Needs |
|---|---|---|---|
The URL https://mcp2.getsales.io/mcp/public | Clients that speak streamable HTTP: claude.ai, Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code | OAuth in the browser, or an API key header | Nothing to install |
The npm launcher @getsales/outreach-mcp | Clients that can only start a command | OAuth, or GETSALES_API_KEY | Node.js 18 or newer |
The Docker image getsalesio/outreach-mcp | A host without Node.js | GETSALES_API_KEY only | Docker |
1. Get an account. Sign up for GetSales, or use the workspace you already have.
2. Add the server to your client. Claude Desktop and Cursor read the bare URL from their config file (examples/claude_desktop_config.json, examples/cursor_mcp.json):
{
"mcpServers": { "getsales": { "url": "https://mcp2.getsales.io/mcp/public" } } }
In Claude Code it takes one command:
claude mcp add --transport http getsales https://mcp2.getsales.io/mcp/public
On claude.ai, open Settings, Connectors, Add custom connector, and paste the same URL.
You paste no key. The first call comes back with a WWW-Authenticate challenge, the client registers itself (dynamic client registration), and the GetSales consent screen opens in your browser. Sign in, pick the workspaces the client may act in, and click Allow.
A client with no browser at hand (CI, a server, a script) sends an API key instead, made in the app under Settings, API keys:
claude mcp add --transport http getsales https://mcp2.getsales.io/mcp/public --header "Authorization: Bearer gs_live_..."
Use one way per connection. A client that runs OAuth and also sends a fixed header overwrites its OAuth token with that header on each request.
A client that can only start a command runs the launcher (examples/claude_desktop_config.npx.json). It does the same OAuth flow, or uses GETSALES_API_KEY when you put the key in its env. The key goes to the server as the bearer and never onto a command line, so a process list or the client's log of the launcher does not show it:
{
"mcpServers": { "getsales": { "command": "npx", "args": ["-y", "@getsales/outreach-mcp"] } } }
The Docker image runs the same launcher and signs in with a key only (examples/claude_desktop_config.docker.json). With -e and the bare variable name, docker hands the container the key from the client's env, and the key stays off the docker command line:
{
"mcpServers": { "getsales": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "GETSALES_API_KEY", "getsalesio/outreach-mcp"], "env": { "GETSALES_API_KEY": "gs_live_..." } } } }
OAuth cannot finish in the container: after the consent page your browser comes back to localhost, which is your machine, while mcp-remote waits for that answer on the container's own loopback. So without a key the container stops at once and says why. For OAuth, give the client the URL or run the npm launcher.
3. Ask in plain words.
"Build a table of heads of marketing at SEO agencies in Germany, add a work email column and tell me what it costs before anything runs."
The agent finds the tools and chains them: a table, an AI search as its source, the email column, the estimate. Then it stops and waits for your word. Every client step by step, ChatGPT, VS Code and Codex included: CONNECT.md.
Can I install it as a Claude Code or Cursor plugin?
Yes. This repository is a plugin for both (.claude-plugin/plugin.json, .cursor-plugin/plugin.json), and it brings two pieces:
- The hosted server at
https://mcp2.getsales.io/mcp/public, from.mcp.json. - The
getsalesskill and its worked flows. The skill teaches the agent to look a tool up before it calls it, to price paid work and wait for a yes, to show you the preview of a dangerous tool before it confirms, and to read an error before it calls again.
Claude Code loads the plugin from a clone of this repository for one session:
claude --plugin-dir <path to the clone>
For Cursor, copy the plugin files from the clone into Cursor's local plugin folder:
mkdir -p ~/.cursor/plugins/local/getsales
cp -R .cursor-plugin .mcp.json skills assets ~/.cursor/plugins/local/getsales/
Then run Developer: Reload Window. The skill and the server show up under Customize.
The plugin holds no key and asks for no settings: the consent page opens on the first tool call.
What can my agent do with it?
The server keeps the tools of the workspace in toolsets, and an agent loads only what a task needs. It calls search_tools with the object and the action in plain words, reads the definition it picked (describe_tool, or search_tools with detail: "full"), then runs the tool through call_tool. list_toolsets is the map.
The toolsets of the workspace, by area:
Playtables: tables, people, enrichment and workflows
| Toolset | What the agent works with |
|---|---|
playtables.tables | Tables, saved views and how each table is doing |
playtables.columns | Enrichment and AI columns, cells, runs and cost estimates |
playtables.rows | People, companies and the feed of what happened to each |
playtables.crm | Pipeline stages, notes, tags and the do-not-contact list |
playtables.sources | Where rows come from: AI search, CSV imports, webhooks |
playtables.workflows | Workflows: authoring, validation, publishing, pause and resume |
playtables.workflow-records | Where each person stands in a workflow, and its tasks |
The inbox, sender profiles and the AI SDR
| Toolset | What the agent works with |
|---|---|
inbox | Threads, messages, the AI SDR's drafts, tasks, the person timeline, and who a thread is with |
sender-profiles | Your sender profiles, their variables, and what each did today and day by day |
ai-sdr.agents | Your team's AI SDR agents, their scenarios, plans and runs |
ai-sdr.training | The answers the AI SDR gives and their source documents, and what it learned: examples, hints, fixes and tests |
Signals
| Toolset | What the agent works with |
|---|---|
signals | Sessions and visitors, identified to a person or a company, and the plays that react to a table's facts |
The workspace: the Settings and Admin panels
| Toolset | What the agent works with |
|---|---|
workspace.team | Your account, workspaces, members and invitations, the notification feed, and website reads for onboarding |
workspace.access | The API keys that stand and the apps a person connected |
workspace.billing | Subscription, invoices, payment methods, credit balance and spend |
workspace.website-tracking | Tracking setup: sites, key pages, tracked events, settings |
workspace.integrations | Data providers and their prices, your own connections and HTTP tools, the call log |
workspace.webhooks | Webhook subscriptions and their deliveries |
workspace.whitelabel | White label brands, client workspaces, certificates |
Things to ask once it is connected:
- "How is the Berlin agencies table doing this month, and where do people drop out?"
- "Which threads are waiting for me, and what did the AI SDR draft for each?"
- "Who visited the pricing page this week and has not replied?"
- "Draft a workflow for the Q4 view: an email, two days of waiting, a follow-up. Show it to me before you publish."
- "How many credits do we have left, and what did last week's enrichment spend?"
- "Subscribe our endpoint to new replies and fire a test event."
Which tools ask for a confirm first?
The ones the server marks dangerous. Their first call changes nothing and answers a preview of what would happen, with a commit_token. The same call again with that token runs it. The token works once, for that tool, those arguments and that workspace, and it expires after 300 seconds. Marked dangerous today: each tool that deletes or cancels something, a conversation merge, a thread's counterpart put on the stoplist, a site key or an ingest key rotated, a subscription change, a connected app revoked, a webhook created, changed or replayed, publishing or resuming a workflow, one person resumed, restarted or taken out of a workflow, a company taken off a table, a website visitor unlinked from a person, and an AI SDR agent changed, one of its scenarios reset or its examples forgotten.
These run on their first call, with no preview:
- Paid work. A table run (
create_playtable_runwith typeenrich) spends credits as it goes.estimate_creditsprices it first, and itsmax_budgetcaps it, but a run sent withoutmax_budgethas no cap. An AI search source (create_data_source) spends credits on its result pages with no estimate and no cap. A column withconfig.auto_run: truefills each row that lands, outside any run's budget, held only by the column's own daily credit cap when one is set.
-