sharpspring-mcp-server
An open-source MCP server for the SharpSpring API (Constant Contact Lead Gen & CRM) that enables AI clients to read and write Leads, discover custom fields, and call any documented API method.
README
sharpspring-mcp-server
An open-source MCP (Model Context Protocol) server for the SharpSpring API, now branded Constant Contact Lead Gen & CRM. It lets any MCP-compatible AI client (Claude Desktop, Claude Code, Cursor, etc.) read and write Leads, discover custom fields, and call any other documented SharpSpring API method.
This is an independent, community project. It is not affiliated with, endorsed by, or supported by SharpSpring or Constant Contact.
Design goals
- No account-specific configuration baked in. Every credential comes from environment variables at runtime. No hardcoded custom field names, account IDs, or other values belonging to any one SharpSpring account.
- Generic by default. Tools map to SharpSpring's standard, documented API methods and object shapes only — nothing bespoke.
- Custom fields stay dynamic. Since every SharpSpring account has its own custom fields, this server never assumes field names. Use
sharpspring_get_fieldsto discover a given account's fields (system + custom) at runtime, then reference them bysystemName.
Setup
npm install
npm run build
Copy .env.example to .env and fill in your own credentials (generate them in SharpSpring under API Keys):
cp .env.example .env
SHARPSPRING_ACCOUNT_ID=your-account-id
SHARPSPRING_SECRET_KEY=your-secret-key
# Optional: v1 (timezone follows the account's Company Profile) or v1.2 (UTC, default)
SHARPSPRING_API_VERSION=v1.2
Using with an MCP client
Once published to npm, you can run it directly with npx — no local clone needed:
{
"mcpServers": {
"sharpspring": {
"command": "npx",
"args": ["-y", "sharpspring-mcp-server"],
"env": {
"SHARPSPRING_ACCOUNT_ID": "your-account-id",
"SHARPSPRING_SECRET_KEY": "your-secret-key"
}
}
}
}
Or, running from a local clone/build, point at the built entry point instead:
{
"mcpServers": {
"sharpspring": {
"command": "node",
"args": ["/absolute/path/to/sharpspring-mcp-server/build/index.js"],
"env": {
"SHARPSPRING_ACCOUNT_ID": "your-account-id",
"SHARPSPRING_SECRET_KEY": "your-secret-key"
}
}
}
}
Never commit real credentials — pass them as environment variables as shown above.
Tools
| Tool | SharpSpring method | Description |
|---|---|---|
sharpspring_get_fields |
getFields |
Discover lead/account/opportunity/campaign fields, including custom fields and their systemName. |
sharpspring_get_leads |
getLeads |
List/filter leads (by id, emailAddress), up to 500 per call. |
sharpspring_get_lead |
getLead |
Fetch a single lead by id. |
sharpspring_create_leads |
createLeads |
Create up to 500 leads. |
sharpspring_update_leads |
updateLeads / updateLeadsV2 |
Update up to 500 leads by id. |
sharpspring_delete_leads |
deleteLeads |
Delete leads by id. |
sharpspring_call |
any | Generic escape hatch: call any documented SharpSpring method (Accounts, Campaigns, Opportunities, Lists, Notes, Tasks, DealStages, Products, Emails, ...) by name with a raw params object. |
Only Leads have dedicated, ergonomic tools today. Every other standard SharpSpring object (Accounts, Campaigns, Opportunities, Lists/ListMembers, Notes, Tasks, ...) is already reachable through sharpspring_call and is a natural next PR — see Contributing.
API notes
- Endpoint:
https://api.sharpspring.com/pubapi/{version}/, JSON-RPC-style POST requests, auth viaaccountID/secretKeyquery params. - Object-level errors (e.g. "Entry already exists") come back inside a successful response, nested under
result.creates[].error/result.updates[].error/result.deletes[].error— always check these, not just the top-levelerrorfield. - Rate limits: 50,000 requests/day, 10 requests/second, 500 objects per query. This server does not implement client-side throttling or retries — callers are responsible for respecting these limits.
Contributing
Pull requests are welcome, especially dedicated tools for other standard objects (Accounts, Campaigns, Opportunities, Lists, Notes, Tasks). Keep additions generic and account-agnostic: no hardcoded field names, account IDs, or other environment-specific values.
License
MIT — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。