Competiflow MCP Server
The Competiflow MCP Server lets AI clients manage competitor monitoring via Competiflow's API. Here's what you can do:
Workspace Management
List, create, and refresh workspaces (queuing fresh checks for all active monitors)
Get weekly digests summarizing competitive changes and opportunities
Competitor Tracking
Add competitors by homepage URL with async discovery (idempotent on duplicates)
List, read, update (cadence/status), or permanently delete competitors
Poll discovery status until completion; handles concurrent discovery conflicts
Monitor Control
Create manual monitors for specific URLs; list, read, update (URL, type, cadence, status, severity), and delete them
Trigger on-demand checks for a specific monitor or all active monitors in a workspace
Supports monitor types (homepage, blog, docs, changelog, pricing) and cadences (hourly, six-hourly, daily, weekly)
Pause monitors/competitors to preserve history; delete removes everything permanently
Change Feed & Triage
Browse a cursor-paginated feed of detected changes, filterable by date, severity, monitor type, and review status
Get full change details, optionally including capture evidence, extracted markdown, or raw before/after diffs
Triage changes by marking them as
unreviewed,acknowledged, ordismissed
AI Integration
Works seamlessly with MCP-compatible clients (e.g., Cursor, Claude Desktop, Windsurf) using a single API key
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Competiflow MCP ServerShow me recent changes from my competitors."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Competiflow MCP Server
MCP (Model Context Protocol) server for Competiflow. Use competitor monitoring as tools in Cursor, Claude Desktop, Windsurf, and any MCP-compatible client.
Track competitors, run discovery, read the interpreted change feed, triage items, and pull workspace digests without leaving your AI client.
Setup
Create an API key in the Competiflow dashboard under API keys, then add the server to your client config. COMPETIFLOW_API_KEY is the only variable you need.
Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"competiflow": {
"command": "npx",
"args": ["-y", "@competiflow/mcp-server"],
"env": {
"COMPETIFLOW_API_KEY": "sk_live_your_key_here"
}
}
}
}Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"competiflow": {
"command": "npx",
"args": ["-y", "@competiflow/mcp-server"],
"env": {
"COMPETIFLOW_API_KEY": "sk_live_your_key_here"
}
}
}
}Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"competiflow": {
"command": "npx",
"args": ["-y", "@competiflow/mcp-server"],
"env": {
"COMPETIFLOW_API_KEY": "sk_live_your_key_here"
}
}
}
}Related MCP server: FundzWatch MCP Server
Available Tools
Tool | API | Description |
|
| List workspaces with review counts |
|
| Create a workspace |
|
| Add a competitor by homepage URL. Async discovery, idempotent on duplicate URL |
|
| List competitors with monitors and |
|
| Read one competitor |
|
| Set cadence or status on all its monitors |
|
| Remove a competitor and all its history |
|
| List monitors with status, cadence, and |
|
| Read one monitor. Pass |
|
| Add a manual monitor on a specific URL |
|
| Update URL, cadence, status, or |
|
| Remove a monitor and all its history |
|
| Queue an on-demand check |
|
| Queue checks for active monitors |
|
| Change feed with |
|
| Full change. Pass |
|
| Set |
|
| Weekly workspace summary |
Typical flow
list_workspacesorcreate_workspace.add_competitorwith a homepage URL.get_competitoruntildiscovery_statusiscompleted.refresh_workspaceorcheck_monitorto pull fresh data.list_changeswithsince=7dandmin_severity, orget_digestfor a summary.get_changewithincludewhen you need evidence.update_changeto acknowledge or dismiss items.
Discovery and idempotency
add_competitor starts discovery in the background and returns an acknowledgement, not the finished result. Poll get_competitor until discovery_status is completed.
A workspace runs one discovery at a time. Posting the same homepage URL again returns the existing competitor without starting a second run. If a different competitor is still discovering, the call returns 409 discovery_in_progress with active_competitor_id so you know which one to poll.
Evidence with include
get_change and get_monitor accept an include array to attach the underlying capture in one call:
Token | Available on | Returns |
|
| Extracted fields from the snapshot |
|
| Page markdown from the snapshot |
|
| Before and after diff for the change |
For a change the capture is the post-change page. For a monitor it is the latest successful check, which is the current baseline.
Delete versus pause
delete_monitor and delete_competitor are permanent. They remove the monitor or competitor along with its check runs, snapshots, and changes. To stop checks while keeping intel history, call update_monitor or update_competitor with status: paused instead.
Agent guidelines (for AI clients)
Poll discovery, do not assume: after
add_competitor, pollget_competitoruntildiscovery_statusiscompletedbefore reading changes. On409, poll theactive_competitor_idfrom the error.Filter the feed: pass
since(1d,7d,30d, or ISO8601),min_severity,monitor_type(homepage,blog,docs,changelog,pricing), andreview_statustolist_changesinstead of pulling everything. Usemeta.countsfor inbox totals andnext_cursorto page.Interpretation fields: changes and digest items expose
why_it_mattersfor competitive context.recommended_actionwas removed from the API.Fetch evidence on demand: only add
includetoget_changeorget_monitorwhen you need the underlying capture. It adds payload.Prefer pause over delete: default to
status: pausedwhen a user wants to stop a monitor. Reservedelete_*for permanent removal, since it drops history.
How it works
The server translates each tool call into a Competiflow v1 API request and returns structured JSON. Your agent sees interpreted changes, severity, and why it matters instead of raw page scrapes.
AI Agent → MCP Tool Call → Competiflow API → Interpreted Change Feed → Structured Response → AI AgentEnvironment variables
Variable | Required | Description |
| Yes | Your Competiflow API key ( |
Get an API key
Sign up at competiflow.com and create a key under API keys.
Development
npm install
npm run build
COMPETIFLOW_API_KEY=sk_live_... node dist/index.jsLicense
MIT
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
- Alicense-qualityCmaintenanceEnables AI-powered competitor monitoring and daily schedule optimization by integrating news data with calendar and task management tools like Google Calendar, Jira, and Asana. It allows users to automate intelligence gathering and generate structured daily plans based on strategic priorities.Last updatedMIT
- AlicenseAqualityBmaintenanceProvides real-time business event intelligence and AI-scored sales leads to help users track funding rounds, acquisitions, and executive hires. It enables AI agents to generate strategic market briefs and manage company watchlists for predictive business insights.Last updated7512MIT
- AlicenseAqualityDmaintenanceProvides access to 9 AI executives offering board-ready business intelligence, competitor analysis, trend monitoring, and more via agent-payable endpoints.Last updated5MIT
- Alicense-qualityBmaintenanceCompetitor Tracker & Co. watches your competitors' websites and reports what changed: pricing, product, messaging and corporate moves, crawled weekly and filed as a tagged, ranked report. This server gives your agent the same intelligence: subscribe to competitors, read the change feed, and pull page snapshots.Last updatedMIT
Related MCP Connectors
Track competitors from your AI assistant: change feed, page snapshots, labels and alerts.
Live market intelligence & AI content strategy: trends, competitor moves, content calendar.
Competitive intelligence - track what competitors ship each week. 8 tools, 3 prompt workflows.
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/nyku/competiflow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server