SeaTalk MCP Server
SeaTalk MCP 服务器
一个连接到 SeaTalk 开放平台 API 的 MCP 服务器,为你提供 8 个工具:
工具 | 功能 |
| 通过机器人向 SeaTalk 用户发送私信 |
| 向群聊发送消息 |
| 列出机器人已加入的所有群组 |
| 获取特定群组的详细信息 |
| 读取群组中的最近消息(最多 7 天) |
| 通过邮箱查找员工代码 |
| 按 ID 检索特定消息 |
| 读取线程中的消息 |
前提条件
Node.js 18+ — 从 nodejs.org 下载(选择 LTS 版本)
SeaTalk 应用凭据 — 来自 open.seatalk.io:
创建一个应用/机器人
复制你的 App ID 和 App Secret
启用消息和通讯录功能
Related MCP server: DingTalk MCP Server
快速开始(本地)
# Install dependencies
npm install
# Build the TypeScript code
npm run build
# Set your credentials and run
SEATALK_APP_ID=your_id SEATALK_APP_SECRET=your_secret npm start服务器在 http://localhost:3000/sse 上启动。
部署到 Railway(推荐非开发者使用)
前往 railway.app 并注册(提供免费套餐)
点击 "新建项目" → "从 GitHub 仓库部署"
连接你的 GitHub 并上传此代码(或使用"从本地部署")
转到 "变量" 选项卡并添加:
SEATALK_APP_ID= 你的 App IDSEATALK_APP_SECRET= 你的 App SecretPORT= 3000
Railway 将自动检测 Dockerfile 并部署
复制 Railway 提供的公共 URL(例如
your-app.up.railway.app)你的 MCP 端点是:
https://your-app.up.railway.app/sse
部署到 Render
前往 render.com 并注册
点击 "新建" → "Web 服务"
连接你的仓库或上传代码
设置 "构建命令":
npm install && npm run build设置 "启动命令":
npm start添加环境变量:
SEATALK_APP_ID= 你的 App IDSEATALK_APP_SECRET= 你的 App Secret
部署并复制 URL
连接到 Migoo
部署后,将其添加为自定义 MCP:
使用 URL:
https://YOUR-DEPLOYED-URL/sse就这样——工具将自动出现
项目结构
seatalk-mcp-server/
├── src/
│ └── index.ts ← Main server code (all tools + API client)
├── package.json ← Dependencies
├── tsconfig.json ← TypeScript config
├── Dockerfile ← For Docker-based deploys
├── Procfile ← For Railway/Heroku
├── .env.example ← Template for env vars
└── README.md ← This fileThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Feishu/Lark platform APIs for automation scenarios including message management, document operations, calendar scheduling, group management, and Bitable operations through natural language.7,855MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to interact with DingTalk workspaces to search for users, retrieve detailed employee information, and send private messages. It bridges the Model Context Protocol with DingTalk's internal enterprise APIs for seamless workspace communication.85MIT
- AlicenseNot gradedqualityDmaintenanceEnables real-time Feishu message monitoring, sending, file upload to cloud documents, and supports async and scheduled tasks via MCP.5MIT
- AlicenseAqualityCmaintenanceEnables AI clients to send, read, reply, and search messages on Feishu/Lark as the user's own identity using MCP tools.720MIT
Related MCP Connectors
Search, document and execute authenticated API calls across 700+ apps via one MCP server
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.
Manage Gmail messages, threads, labels, drafts, and settings from your workflows. Send and organiz…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentp-amateur/seatalk-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server