Competitive intelligence — track what competitors ship each week. 8 tools, 3 prompt workflows.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"com-meertrack-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Competitive intelligence — track what competitors ship each week. 8 tools, 3 prompt workflows.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for com.meertrack/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
@meertrack/mcpModel Context Protocol server for Meertrack. Ask your agent "what did my competitors ship this week?" from Claude, Cursor, Claude Code, VS Code, Windsurf, Cline, ChatGPT, or anywhere that speaks MCP.
Wraps the Meertrack v1 REST API as 8
read-only tools and 3 prompt workflows. No backend changes, same
mt_live_ keys, same rate limits.
| Local (stdio) | Remote (Streamable HTTP) | |
|---|---|---|
| Setup time | 30 seconds (paste a JSON block) | 10 seconds (paste a URL) |
| Best for | Individual Pro customers; all Claude Desktop plans; any IDE on your laptop | Team/Enterprise custom connectors; Claude.ai web; remote-capable IDEs |
| Runs where | Your machine (npx -y @meertrack/mcp) | Meertrack's Fly.io fleet (https://mcp.meertrack.com/mcp) |
| Auth | MEERTRACK_API_KEY env var | OAuth 2.1 (browser flow, recommended) or Authorization: Bearer mt_live_… header |
| Plan gating | Works on Claude Pro, Team, Enterprise | Claude Desktop "Add custom connector" is Team/Enterprise only |
If you're on Claude Pro, use the local (stdio) path. The "Add custom
connector" button in the Claude Desktop settings is gated to Team/Enterprise,
and pasting https://mcp.meertrack.com/mcp there won't do anything on a Pro
plan.
Mint a production key at Settings → API Keys in the Meertrack app. Keys
start with mt_live_. Only production keys work; there is no mt_test_
flavour.
Rate limits. Each API key shares a 60 requests/minute budget enforced upstream. If you run the MCP from multiple clients at once (Claude Desktop + Cursor + a background agent) they all draw from the same bucket. Mint a separate key per workstation or per agent to isolate budgets. The tool-error message on 429 includes both a human-readable reset time and the raw
X-RateLimit-Resetepoch so the agent can back off automatically.
All local-mode clients use the same shape: npx -y @meertrack/mcp with
MEERTRACK_API_KEY in the environment. What differs is the config file and
the surrounding JSON key.
Drop-in copies of every config file below live in examples/.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"meertrack": {
"command": "npx",
"args": ["-y", "@meertrack/mcp"],
"env": {
"MEERTRACK_API_KEY": "mt_live_..."
}
}
}
}
Gotcha: Claude Desktop only re-reads this file on launch. Fully quit (⌘Q on macOS) and reopen. Reloading the window is not enough.
Edit ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"meertrack": {
"command": "npx",
"args": ["-y", "@meertrack/mcp"],
"env": {
"MEERTRACK_API_KEY": "mt_live_..."
}
}
}
}
claude mcp add meertrack npx -y @meertrack/mcp \
--env MEERTRACK_API_KEY=mt_live_...
Edit .vscode/mcp.json (per-workspace) or the user settings equivalent:
{
"servers": {
"meertrack": {
"command": "npx",
"args": ["-y", "@meertrack/mcp"],
"env": {
"MEERTRACK_API_KEY": "mt_live_..."
}
... [View full README on GitHub](https://github.com/meertrack/meertrack-mcp#readme)