axure-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| axure_healthB | Health check for Axure MCP server runtime. |
| axure_fetchC | Fetch visible text and image URLs from a public Axure share link. |
| axure_summary_promptC | Build an AI-ready summary prompt from a public Axure link. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.