
Curviate
com.curviate由 curviate.com 發布官方發布者v0.3.0更新於 Oct 25, 2026
LinkedIn actions for AI agents: search, messaging, posts and invites, as hosted MCP tools.
概覽
託管式 MCP 伺服器,透過 Curviate 工作區讓 AI 助理執行 LinkedIn 操作:搜尋、訊息、發文與邀請連結。
- 可以做什麼
- 搜尋 LinkedIn 人物與潛在客戶,並在工作區啟用且帳號擁有對應產品時使用 Sales Navigator 與 Recruiter 工具集。讀取並整理 LinkedIn 訊息串,起草回覆。以使用者口吻起草並發布貼文。起草並送出邀請連結與邀請附註。以上皆透過單一託管端點以原生工具提供,無需本機安裝。
- 適用情境
- 適合需要助理代表使用者在 LinkedIn 內作業的情境:潛在客戶開發與名單研究、收件匣整理與回覆起草、貼文起草、邀請連結外聯。較適合已使用 Curviate 並連結 LinkedIn 帳號的團隊,而非只想讀取公開資料的人。
- 執行需求
- 遠端 Streamable HTTP 端點,無需安裝。需要 Curviate 工作區與至少一個已連結的 LinkedIn 帳號。驗證方式為 OAuth 2.1(首選),或以 Authorization Bearer 標頭傳送 Curviate API 金鑰,最後手段是 token 查詢參數。Sales Navigator 與 Recruiter 工具集須依工作區開啟,且帳號須擁有對應產品。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Curviate,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/com.curviate%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"curviate": {
"type": "http",
"url": "https://app.curviate.com/mcp"
}
}
}README
LinkedIn actions for AI agents, as MCP tools. One hosted URL, nothing to install.
[docs curviate.com] [transport streamable http] [auth oauth 2.1] [hosting eu] [license mit]
Connect in 30 seconds
Point any MCP client that speaks remote Streamable HTTP at one URL:
Sign in with OAuth where the client offers it, otherwise send your Curviate API key as an Authorization: Bearer header. Your agent then has LinkedIn search, messaging, posts and connection requests as native tools. Sales Navigator and Recruiter tools are off by default and switch on per workspace, and they answer only for a connected account that holds the product: see Toolsets.
You need a Curviate workspace and one connected LinkedIn account. Full walkthrough: MCP quickstart.
Your client
Claude Code
OAuth:
Then run /mcp in Claude Code, select curviate, choose Authenticate, and approve access in the browser.
API key:
Your shell expands $CURVIATE_API_KEY when you run that command, so the key itself lands in Claude Code's config file. Prefer the OAuth path above unless you need a key.
Check either setup with claude mcp list: curviate reads Connected.
Details and caveats: docs.curviate.com/reference/mcp/client-setup#claude-code
Codex
OAuth:
Codex prints an authorization URL. Open it, sign in to Curviate, and approve access. To sign in again later, run codex mcp login curviate.
API key, read from the environment each time Codex connects:
Check with codex mcp list.
Details and caveats: docs.curviate.com/reference/mcp/client-setup#codex
Gemini CLI
OAuth:
Then start gemini, run /mcp auth curviate, open the printed URL, sign in to Curviate, and approve access.
API key:
Keep the single quotes: Gemini CLI stores ${CURVIATE_API_KEY} as written and fills it from the environment when it connects, so the key stays out of the settings file.
Check with gemini mcp list: curviate reads Connected. Gemini CLI will not start MCP servers in a folder you have not trusted, where the server reads Disabled instead.
Details and caveats: docs.curviate.com/reference/mcp/client-setup#gemini-cli
Another client
Any client that speaks remote Streamable HTTP can connect. Try OAuth with the bare URL first, then the Authorization: Bearer header. A client that connects but fails tool calls with 401 is usually sending the header only on connect: see Troubleshooting.
Authentication
Your API key is a full-access workspace credential: anyone holding it can act on every LinkedIn account in the workspace. Create, rotate and revoke it from the key chip in the dashboard top bar, keep it in an environment variable, and reference the variable from the client config rather than the literal key.
Full rules: Authentication.
Things to ask your agent
Links
License
MIT. See LICENSE.
來源:README.md,提交 ea0d307
工具
0版本歷史
1- v0.3.0最新Sep 17, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分