What it does
Find LinkedIn prospects, draft outreach, and run human-paced campaigns from your AI agent.
- Connects 在云端运行
- Account or key Sign in to the service when you connect (OAuth)
- Category 营销与社交媒体
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 21/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 41/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Omentir。按照 https://mcp.popnx.com/i/vanshyadav1408-omentir.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(omentir.com) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称OmentirRemote MCP server URL · 地址https://omentir.com/api/agent/v1/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsOmentir
试一试
用 Omentir 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Omentir,或回答中出现 Omentir 的工具名称,就表示连接成功
菜单名称已于 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 · 名称OmentirConnection · 地址https://omentir.com/api/agent/v1/mcp在聊天中选择 Omentir
开启新聊天,输入前先从插件列表中选择 Omentir
试一试
用 Omentir 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Omentir,或回答中出现 Omentir 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user omentir https://omentir.com/api/agent/v1/mcp在 Claude Code 中输入 /mcp
应能看到 Omentir 在列表中并显示已连接
试一试
用 Omentir 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Omentir,或回答中出现 Omentir 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 Omentir 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Omentir,或回答中出现 Omentir 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 Omentir 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Omentir,或回答中出现 Omentir 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://omentir.com/api/agent/v1/mcpJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user omentir https://omentir.com/api/agent/v1/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"omentir": {
"url": "https://omentir.com/api/agent/v1/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"omentir": {
"type": "http",
"url": "https://omentir.com/api/agent/v1/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 vanshyadav1408 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于昨天
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 548 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
云端地址最近 4 次检查中有 4 次响应 · 最近一次 548 ms · 检查于 2026年11月18日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/vanshyadav1408-omentir)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“营销与社交媒体”中的其他服务器比较i
- 星标数多于此分类中其他 4175 个服务器的 98%
- 发布到注册中心的时间比此分类中其他 4175 个服务器的 33% 更新
- 基础检查结果等于或优于此分类中其他 4175 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Omentir 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于昨天,最新版本(1.1.0)于2个月前进入注册中心。
哪些应用可以使用它?
支持 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.
| 本项 Omentir | 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、图片和脚本已被移除。链接会离开本站。
Omentir
Omentir is an open-source alternative to LinkedIn outreach and automation tools like HeyReach and Gojiberry.
It's an AI sales workspace for finding qualified LinkedIn prospects, drafting contextual outreach, running human-paced campaigns, and handling replies — but you own the code and run it on your own infrastructure.
Use the managed product at omentir.com, or self-host the same application code with your own Firebase, Gemini, and Typesafe accounts and, in production, a proxy for LinkedIn traffic.
Omentir reaches LinkedIn through its own client, which ships in this repo. Earlier releases used Unipile for that; it is no longer needed. See LinkedIn client.
One codebase: hosted cloud and self-host share this repo. RUN_LOCALLY=TRUE switches auth, billing, marketing, and hosted-only mail off. Public brand contacts for omentir.com stay in source on purpose (see src/lib/hosted-identity.ts); they are not used for self-hosted operation.
Connect from other AI apps (Claude, ChatGPT, Grok, Grok Bot, Cursor, …)
People use Omentir from chat and coding agents without sharing LinkedIn passwords:
- In Omentir: connect LinkedIn and fill Workspace.
- Chat apps (Claude, ChatGPT, Grok): Settings → Connectors → add
https://omentir.com/api/agent/v1/mcp→ sign in and approve Connect workspace → enable tools in the chat. No API key. - Grok Bot (the always-on teammate app, not grok.com chat): Settings → Plugins → search Marketplace for Omentir. If it is not listed, add the same MCP URL as a custom server → approve Connect workspace. Do not sign LinkedIn into the Bot computer. Grok Bot integration.
- Cursor / Claude Code / scripts: create a key on the API page and send
Authorization: Bearerto the MCP endpoint or REST/api/agent/v1/*. - Ask the assistant to create a classic lead finder or a Steal Customers agent (
mode: steal_customers+ competitor company URLs). If you have more than one company, ask it to list workspaces and switch.
Docs: MCP integration, Agent API, agents.md (machine guide), OpenAPI.
Self-hosting
Omentir is self-hostable with external managed services. It is not offline or dependency-free. You provide Firebase/Firestore, a sticky residential proxy for LinkedIn traffic in production, either a Gemini API key or a Google Cloud Vertex AI project, and a Typesafe API key for lead scoring. You do not need a LinkedIn API vendor.
Self-hosting removes the Omentir subscription, but Firebase, Google AI, Typesafe, and the proxy can still cost money.
Quick start on localhost
Install Git and either Docker with Docker Compose, or Bun 1.3. Then clone and configure the project:
git clone https://github.com/vanshyadav1408/Omentir.git
cd Omentir cp .env.example .env
Open .env and fill in every uncommented blank value. Complete the provider setup below before starting the server.
Generate independent secrets with:
openssl rand -base64 48
Use that (or a password manager) for at least:
LOCAL_SESSION_SECRET(required)LOCAL_APP_PASSWORD(required unless you explicitly allow open access — see Access control)CRON_SECRET(required unless automation is fully disabled)LINKEDIN_SESSION_KEY(required; exactly 32 bytes, so generate it withopenssl rand -base64 32)
LINKEDIN_PROXY_URL is required whenever the server runs in production mode. That includes the Docker image and bun start, even on localhost. Only bun run dev starts without it.
For an initial setup with all automation disabled, leave CRON_SECRET blank and set AUTOMATION_DISABLED=true instead. Keep ENABLE_LIVE_AUTOMATION=false until dry-run output has been reviewed.
Run with Docker
Docker is the supported self-hosting path. Omentir runs on amd64 and arm64. The image includes Chromium, which LinkedIn sign-in needs.
docker compose up --build -d
docker compose logs -f omentir
Open http://localhost:3000. Press Ctrl+C to exit the log view without stopping Omentir. Stop the server later with docker compose down.
Port binding: Compose publishes the app as 127.0.0.1:3000:3000 only. That means the container is reachable from the same machine (http://localhost:3000), not from other devices on your LAN or the public internet. This is intentional: a misconfigured or passwordless instance must not become reachable just because Docker started.
To expose the app on a real host (LAN/VPS):
- Put HTTPS reverse proxy (Caddy, nginx, Traefik, etc.) on the public interface.
- Proxy to
127.0.0.1:3000(or change the Compose bind only if you understand the risk). - Set
APP_BASE_URLto the exact public HTTPS origin (no trailing slash). - Keep a strong
LOCAL_APP_PASSWORD(do not enable open access on a public URL).
Run with Bun
For local development:
bun install
bun run dev
For a production-style local server:
bun install
bun run build bun start
Open http://localhost:3000. Sign in with LOCAL_APP_PASSWORD unless you opted into open access (see below).
Outside Docker, connecting a LinkedIn account needs Chrome or Chromium on the same machine. Omentir finds the usual install paths on macOS and Linux. Set LINKEDIN_BROWSER_PATH if yours is somewhere else.
Bun is the package manager and script runner, but bun run dev deliberately starts Next on Node rather than under bun --bun. In dev, Turbopack loads every package in serverExternalPackages (firebase-admin among them) through a hashed specifier such as firebase-admin- /firestore, which only resolves via a loader hook Next installs in Node. Bun's resolver does not run that hook, so bun --bun next dev fails on the first Firestore import with ResolveMessage: Cannot find module. Production is unaffected: built output emits plain requires, so build and start still run under Bun.
Access control (local login)
Self-host mode uses a single workspace and a signed, HTTP-only session cookie (omentir_local_session), not Clerk.
| Setting | Behavior |
|---|---|
LOCAL_APP_PASSWORD set (12+ characters, high entropy) | Login form requires that password. This is the default expectation. |
LOCAL_APP_PASSWORD blank and LOCAL_ALLOW_OPEN_ACCESS unset/false | Startup fails. Blank password is no longer enough to run an unprotected instance. |
LOCAL_ALLOW_OPEN_ACCESS=true and blank password | Explicit opt-in: welcome screen with a “Continue to overview” button (no password). Use only on a trusted machine / private network. |
LOCAL_ALLOW_OPEN_ACCESS=true and password set | Password is still required (open-access flag does not weaken a configured password). |
LOCAL_SESSION_SECRET | Required always. Minimum 32 characters, high entropy. Used to HMAC-sign session tokens. Changing it invalidates all existing sessions. |
Additional login hardening that matters for operators:
- Origin check:
POST /api/local-auth/loginonly accepts requests whoseOriginmatchesAPP_BASE_URL. - Brute-force throttle: wrong passwords are rate-limited per source IP (in-process).
- Post-login redirects: the
?next=return path is sanitized so values like//evil.comcannot open-redirect the browser after sign-in. Only same-origin relative paths (starting with a single/) are allowed. - Cookie flags: session cookies are
HttpOnly,SameSite=Lax, andSecurewhenAPP_BASE_URLis HTTPS.
1. Provider setup
- Create a dedicated Firebase project. Enable Firestore and create a service account. Never reuse the hosted Omentir project.
- Deploy the required indexes with
firebase deploy --only firestore:indexes, or create the indexes from Firestore error links. The source isfirestore.indexes.json.
- Also deploy
firebase deploy --only firestore:rules. Omentir reaches Firestore only through the server-side Admin SDK, so the shippedfirestore.rulesdenies all direct browser/client access. Keep it deployed — it stops anyone from reading or writing your data with a leaked project ID or web API key.
- For production, get a sticky residential proxy that accepts a per-session username (
LINKEDIN_PROXY_URL).bun run devon your own machine works without one. There is no LinkedIn API vendor to sign up for. LinkedIn can restrict automated accounts. - Create a Gemini API key. For Vertex instead, set
GOOGLE_CLOUD_PROJECT,GOOGLE_CLOUD_LOCATION, andGOOGLE_APPLICATION_CREDENTIALS_JSON, enable Vertex AI, and grant the service account Vertex AI User. SetGEMINI_MODELeither way; there is no default in code. - Create a Typesafe API key at
console.typesafe.ai/keys. Typesafe's Jev model decides whether a discovered lead qualifies. Without the key every discovered lead is skipped.
2. Configure
Copy .env.example to .env. Required local settings are validated at server startup:
| Variable | Scope | Secret | Runtime behavior |
|---|---|---|---|
RUN_LOCALLY=TRUE | local | no | Selects built-in single-workspace authentication |
APP_BASE_URL | shared | no | Canonical server URL; HTTPS required off localhost |
LOCAL_APP_PASSWORD | local | yes* | Required access password unless open access is explicitly allowed; minimum 12 characters when set |
LOCAL_ALLOW_OPEN_ACCESS | local | no | Must be exactly true to allow a passwordless welcome screen |
LOCAL_SESSION_SECRET | local | yes | Independent random value, minimum 32 characters |
LOCAL_USER_NAME / LOCAL_USER_EMAIL | local | no | Display identity for the single local workspace |
FIREBASE_PROJECT_ID | shared | no | Dedicated Firebase project |
FIREBASE_SERVICE_ACCOUNT_KEY | shared | yes | Service-account JSON; malformed JSON fails startup |
LINKEDIN_SESSION_KEY | shared | yes | Required. 32 bytes, base64; encrypts stored LinkedIn session cookies |
LINKEDIN_PROXY_URL | shared | yes | Sticky residential proxy URL with a {session} placeholder and an optional {country} one; required in production mode (Docker and bun start) |
LINKEDIN_PROXY_COUNTRY | shared | no | Two-letter country for accounts whose country is unknown. Required when LINKEDIN_PROXY_URL uses {country} |
LINKEDIN_ISP_PROXY_URL | shared | no | Static ISP proxy URL with {port} (and {host} when each IP has its own address). Turns on the static IP pool: one IP per account that never changes, and no new account on a residential IP |
BYTEFUL_API_PUBLIC_KEY / BYTEFUL_API_PRIVATE_KEY | shared | no | Byteful API keys. Keeps the static IP pool in sync with Byteful and, with a budget, buys IPs on its own |
LINKEDIN_PROXY_MONTHLY_BUDGET_USD | shared | no | Most Omentir may spend on bought static IPs per month. Without it nothing is bought |
LINKEDIN_PROXY_SPARES | shared | no | Free static IPs kept ready for new accounts (default 2) |
LINKEDIN_BROWSER_PATH | shared | no | Path to a Chrome or Chromium binary for LinkedIn sign-in. Only needed outside Docker when the browser is not in a usual install path |
GEMINI_API_KEY | local/simple | yes | Gemini Developer API path |
| Vertex variables | shared/advanced | yes | Alternative to GEMINI_API_KEY |
GEMINI_MODEL | shared | no | Required for AI features. The model comes only from this setting |
TYPESAFE_API_KEY | shared | yes | Lead scoring. Without it every discovered lead is skipped |
CRON_SECRET | shared | yes | Required unless automation is disabled; used by the built-in scheduler and job routes |
| ENABLE_LIVE_AUTOMATION | local | no