Skip to main content
Glama
Sign In
axure-mcp-server

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

    • read-website-fast

      snair261
      A
      license
      Not graded
      quality
      A
      maintenance
      Fetches web pages, strips noise, and converts them to clean Markdown with preserved links and optional multi-page crawling, enabling token-efficient web content extraction for AI agents and LLM pipelines.
      MIT

    • 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.
      -

    • read-website-fast

      Sidorov58002
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and LLM pipelines to fetch webpages or crawl sites, extract main content, and convert it to clean, token-efficient Markdown with preserved links. It supports configurable crawling depth, caching, robots.txt compliance, and optional chunking for downstream processing.
      -

    • read-website-fast

      ErikChen91
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to fetch webpages locally, extract main content, and convert it into clean, token-efficient Markdown with preserved links. Supports configurable multi-page crawling, caching, robots.txt compliance, and optional chunking for downstream processing.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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.

    Resources