
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 分