Skip to main content
Glama
Figranium MCP Server

Figranium MCP Server

Official

Related Servers

Alternatives to Figranium MCP Server

  • A
    license
    A
    quality
    D
    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
  • A
    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
    7,781 npm
    3
    MIT
  • 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,340
    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.7/5.0

Scored across 16 tools

Disambiguation4/5

Most tools target clearly distinct resources and actions: task CRUD/execution, template reads, schedule management, and cabinet management. The only mild overlap is among the three schedule status tools (schedule_list, schedule_get_all_status, schedule_get_status), whose boundaries require reading descriptions to separate.

Naming Consistency3/5

All names use snake_case, but verb placement is inconsistent: create_task, list_cabinets, and create_cabinet are verb_noun while task_list, task_update, task_delete, task_execute, template_get, and schedule_set are noun_verb. Still readable and groupable by prefix, but the convention is not uniform.

Tool Count4/5

16 tools covering task lifecycle, scheduling, templates, and cabinets is slightly on the heavy side but each tool maps to a distinct operation. No obvious redundant or filler tools beyond the schedule status trio.

Completeness4/5

Task CRUD plus execution is well covered, and scheduling has list/set/delete/describe/status. Minor gaps remain: only execution_list exists with no per-execution detail retrieval, and cabinets support list/create but no update or delete.

Maintenance

ActivityActive
ResponsivenessSyncing