Skip to main content
Glama
six-ben

axure-mcp-server

by six-ben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to axure-mcp-server

No user-submitted related servers found.

    Related Servers

    • Spider MCP Server

      oeo
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables crawling and extracting clean content from documentation websites with optional LLM-powered analysis for intelligent summaries, code example extraction, and content classification.
      -

    • UI Reviewer MCP

      codepawl
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP-first UI/UX review layer for AI-generated frontends. Enables reviewing web pages via URL, capturing screenshots, extracting layout metrics, and generating structured repair plans for agents.
      22 npm
      Apache 2.0

    • skrape

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
      MIT

    • PicassoWeb

      blackridder22
      A
      license
      A
      quality
      A
      maintenance
      Analyzes and extracts design tokens, assets, and layout from live websites to enable AI clients to faithfully replicate them, with tools for screenshotting, component inspection, and pixel-diff verification.
      14
      14 npm
      MIT

    • icecrawl MCP server

      MrGreenlaw
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables scraping single pages or crawling entire websites, converting content to markdown and optionally extracting structured data with Claude.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: fetching content, checking server health, and building a summary prompt. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent 'axure_' prefix with descriptive suffixes (fetch, health, summary_prompt), using snake_case uniformly. This pattern is predictable and enhances readability.

    Tool Count3/5

    With only 3 tools, the server feels thin for a domain like Axure, which might involve more operations (e.g., navigation, element details). However, it covers basic needs without being excessive.

    Completeness2/5

    The toolset is severely incomplete for interacting with Axure prototypes. It lacks essential operations like navigating pages, retrieving specific elements, or handling interactions, limiting agents to basic fetching and summarization tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources