Competiflow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPETIFLOW_API_KEY | Yes | Your Competiflow API key (sk_live_...) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | GET /v1/workspaces. List workspaces with needs_review_count and monitor totals. |
| create_workspaceB | POST /v1/workspaces. Create a workspace for one product or market. |
| add_competitorA | POST /v1/workspaces/:id/competitors. Add a competitor by homepage URL. Idempotent on duplicate URLs. Returns 409 with active_competitor_id when another discovery is running. |
| list_competitorsA | GET /v1/workspaces/:id/competitors. List competitors with discovery_status and nested monitors (includes last_run on each monitor). |
| get_competitorB | GET /v1/competitors/:id. Read one competitor with monitors and discovery fields. |
| update_competitorB | PATCH /v1/competitors/:id. Set cadence or status on all monitors for this competitor. |
| delete_competitorA | DELETE /v1/competitors/:id. Permanently removes the competitor, its monitors, snapshots, and changes. |
| list_monitorsA | GET /v1/monitors. List monitors in a workspace with health, cadence, and last_run. |
| get_monitorA | GET /v1/monitors/:id. Read one monitor. Pass include for capture or capture_markdown from the latest successful check. |
| create_monitorC | POST /v1/monitors. Add a manual monitor on a specific URL. |
| update_monitorC | PATCH /v1/monitors/:id. Update url, monitor_type, cadence, status, or min_severity. Use status paused to keep history. |
| delete_monitorB | DELETE /v1/monitors/:id. Permanently removes the monitor and all its changes and snapshots. |
| check_monitorB | POST /v1/monitors/:id/check. Queue an on-demand check for one monitor. |
| refresh_workspaceB | POST /v1/workspaces/:id/refresh. Queue checks for all active monitors, or one competitor when competitor_id is set. |
| list_changesC | GET /v1/changes. Cursor-paginated change feed. Response includes meta.counts and max_unreviewed_severity. |
| get_changeA | GET /v1/changes/:id. Full change detail. Pass include for capture, capture_markdown, or raw_diff evidence. |
| update_changeB | PATCH /v1/changes/:id. Set review_status to unreviewed, acknowledged, or dismissed. |
| get_digestC | GET /v1/workspaces/:id/digest. Weekly workspace summary with needs-review items and top opportunities. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action (e.g., competitor vs monitor vs change). There is no overlap; even 'add_competitor' and 'create_monitor' address different entities. An agent can reliably select the correct tool.
All tools follow a consistent verb_noun pattern (e.g., add_competitor, list_changes, update_monitor). Verbs are clear and nouns match resource names without mixing conventions.
18 tools cover the full lifecycle of competitors, monitors, changes, and workspaces. The count feels well-scoped for a monitoring service—not too few to miss functionality nor too many to overwhelm.
The tool surface covers CRUD for competitors, monitors, and changes, plus check/refresh triggers and a digest. However, workspace management is incomplete (no delete or update workspace), creating a minor gap.