Skip to main content
Glama
nyku

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.
      13
      267 npm
      MIT
    • A
      license
      A
      quality
      C
      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
      Competitor 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.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      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 issues