Grips Intelligence MCP Server
Provides access to Grips Intelligence e-commerce analytics data through Model Context Protocol. Enables querying domain performance metrics, channel breakdowns, ad spend data, and device analytics for e-commerce businesses.
README
Grips Intelligence MCP server (v2)
A Model Context Protocol (MCP) server that exposes the Grips Intelligence e-commerce data API to any MCP client — Claude Desktop, Cowork, Claude Code, etc.
v2 is a clean rebuild of v1 with defensive data handling baked in from day one. It fixes the ".map is not a function" class of bugs that v1.x needed a runtime patch to address — thin or unknown domains now degrade to a clean "no data" response instead of crashing the tool call.
What's in it
| Tool | What it does |
|---|---|
grips_get_domain_performance |
Monthly revenue / transactions / sessions / ad cost / AOV / CR / CPC for one or more domains |
grips_get_daily_performance |
Daily revenue / transactions / sessions (limited coverage) |
grips_get_channels |
Organic / Paid Search / Direct / Referral / Social breakdown — timeseries + aggregated |
grips_get_adwords |
Paid-media spend, clicks, and CPC — timeseries + aggregated |
grips_get_devices |
Mobile / desktop / tablet revenue, sessions, CR, AOV |
grips_compare_domains |
Parallel per-domain pull with leaderboard ranking; per-domain errors are isolated |
grips_raw_query |
Escape hatch — send an arbitrary Grips GraphQL query |
All tools default to markdown output for readability. Pass format: "json" for machine-parseable output.
Installation
npm install
The prepare script auto-builds dist/ when you run npm install.
Configuration
Set your Grips API key in the MCP client's server config. For Claude Desktop, that's ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"grips": {
"command": "node",
"args": [
"/ABSOLUTE/PATH/TO/grips-mcp-server-v2/dist/index.js"
],
"env": {
"GRIPS_API_KEY": "your-api-key-here",
"GRIPS_DEFAULT_COUNTRY": "US"
}
}
}
}
Required env:
GRIPS_API_KEY— your Grips API token (sent as thegrips-api-keyheader).
Optional env:
GRIPS_DEFAULT_COUNTRY—US,GB, orDE. Defaults toUSif unset or invalid.
After editing the config, fully quit Claude Desktop (Cmd+Q — not just closing the window) and reopen.
What's different from v1
v1 crashed on a specific API response shape: when Grips returned a thinly-covered or unknown domain, the timeseries field came back as {} rather than null, undefined, or []. The code used (data.timeseries ?? []).map(...), which only guards against null/undefined — not against {}. Result: "data.timeseries ?? []).map is not a function".
v2 routes every payload field through toArray<T>() (for arrays) or toObject<T>() (for dict-shaped responses like the devices endpoint) before use. Any non-array / non-object value falls through to a safe empty default, and the tool returns a clean "no data" response instead of throwing.
Other changes:
- Date normalisation is consistent (every date becomes
YYYY-MM-DDin UTC) across all tools, so rows don't slip across day boundaries in non-UTC timezones. - Currency / integer / percent formatters render
—for missing values instead of$NaNor0.00%. - Error messages now include actionable hints — 401 → "check your API key", 429 → "rate-limited, narrow your window", etc.
- Per-domain error isolation in
grips_compare_domains— one thin domain in an 8-domain compare no longer breaks the other seven. - Character-budget truncation — responses cap at ~200KB with a visible notice so multi-domain pulls don't blow up the context window.
Development
npm run dev # watch mode, rebuilds on change
npm run build # one-shot build to dist/
Testing from the command line
Test that the server boots without errors (it will exit on EOF from stdin):
GRIPS_API_KEY=your-key node dist/index.js < /dev/null
You should see [grips-mcp] grips-mcp-server v2.0.0 ready (default country: US). on stderr and no crash.
For interactive testing, use @modelcontextprotocol/inspector:
npx @modelcontextprotocol/inspector node dist/index.js
API reference
Grips documents their public schema at https://gripsintelligence.com/knowledge-base/api. The queries this server uses are copied verbatim from that page.
Supported countries today: US, GB, DE. Everything else will error at the API.
Licence
Private — not for external distribution.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。