Skip to main content
Glama
Competiflow MCP Server

Competiflow MCP Server

by nyku

Related Servers

Alternatives to Competiflow MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants such as Claude, Cursor, and Codex to pull structured, source-backed, dated competitive intelligence — positioning, pricing, ads, social, reviews, hiring, momentum, and exploitable weaknesses — for any company in the universe, alongside the user's own projects, reports, battlecards, timelines, and evidence. Read-only by default, with optional opt-in competitor creation and plan-gated tools for deeper analysis.
      16
      108 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides real-time account intelligence, deal signals, and strategic openers to AI agents and MCP-compatible orchestrators, enabling automated sales workflows such as pre-call battlecards, deal reactivation, and territory monitoring.
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and work with competitive intelligence and brand monitoring data from a Watchr workspace, including validated insights, reports, monitoring configuration, tags, and member workflows under account permissions.
      3
      MIT

    TDQS

    A4.2/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool maps to a distinct resource+action pair, and the descriptions actively disambiguate the closest neighbours (check_monitor vs refresh_workspace, list_competitors vs list_monitors, list_changes vs get_digest vs get_change, add_competitor vs create_monitor) with explicit 'use X instead' pointers. Pause-vs-delete semantics are also spelled out consistently across the three hierarchies, so an agent can select confidently.

    Naming Consistency4/5

    The set follows a predictable verb_noun pattern (list_/get_/create_/update_/delete_ + resource, plus check_/refresh_ actions), which reads cleanly. The only wrinkle is that creation uses two verbs — add_competitor alongside create_monitor/create_workspace — a minor inconsistency rather than a real hazard.

    Tool Count4/5

    Twenty tools is on the heavy side of the rubric, but it decomposes cleanly: near-complete CRUD across three resources (workspace, competitor, monitor) plus four change/digest tools and two on-demand check tools. Each tool earns its place; nothing looks like a redundant duplicate.

    Completeness4/5

    The surface covers full lifecycle management of workspaces, competitors, and monitors, plus change reading (list_changes, get_change), triage (update_change), and briefing (get_digest) with async discovery/refresh flows handled via polling and explicit status codes. Minor gaps remain: there is no get_workspace for a single workspace by id (only list_workspaces), and change triage is one-at-a-time with no bulk operation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues