Skip to main content
Glama
figranium

Figranium MCP Server

Official

Related Servers

Alternatives to Figranium MCP Server

  • A
    license
    A
    quality
    C
    maintenance
    Agent-native browser control MCP server that enables AI agents to browse and interact with web pages via accessibility tree snapshots and ref ID-based commands.
    15
    2
    MIT
  • F
    license
    A
    quality
    B
    maintenance
    An MCP server that gives Claude direct control of a real browser via Playwright, enabling AI-driven web testing, autonomous test execution, and live failure analysis through natural language.
    8
    4,678 npm
    3
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Skyvern MCP server lets AI agents control a real browser to navigate websites, fill forms, authenticate, and extract structured data. Supports multi-step automation workflows via natural language.
    23,043
    AGPL 3.0
  • A
    license
    Not graded
    quality
    F
    maintenance
    A Model Context Protocol server implementation for Axiom that enables AI agents to query your data using Axiom Processing Language (APL).
    60
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables querying the NFX Signal Investor API to retrieve investor lists, check sizes, and VC firm data, with optional LinkedIn and Crunchbase enrichment.
    -

Related Servers

TDQS

A3.8/5.0

Scored across 16 tools

Disambiguation4/5

The tools are grouped by domain (tasks, schedules, executions, cabinets, browser) and each has a distinct role. However, schedule_list and schedule_get_all_status both surface schedule information and could be confused; otherwise the boundaries are clear.

Naming Consistency3/5

Naming mixes conventions: some tools use verb_noun (create_task, list_cabinets) while most use noun_verb (task_update, schedule_get_status, browser_open). The verbs are specific and readable, but the inconsistent ordering prevents a fully predictable pattern.

Tool Count5/5

16 tools is well-scoped for a browser-automation server that covers task CRUD, execution, scheduling, cabinets, and browser inspection. Each tool has a clear purpose and none feel redundant.

Completeness4/5

Core workflows are covered: task lifecycle, execution, schedules, and cabinets. Minor gaps exist—there is no single-task detail getter, no execution detail view, and no browser close tool—but agents can work around these via task_list and execution_list.

Maintenance

ActivityActive
ResponsivenessNo issues