figma-to-azure
Registry code: d91bb35f17bb2646
Get product information, features, pricing, workflow guides, and FAQs for Figma to Azure — the Figma plugin that creates Azure DevOps work items directly from your designs with automatic screenshot attachment. Search across features, use cases, comparisons (vs manual handoff, vs Zeplin), and pricing plans. Ideal for teams using Figma and Azure DevOps who want to fix broken design handoff.
from a public catalogue that lists it, not from the operator
- endpoint
- https://figmatoazure.com/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is figma-to-azure live?
- Yes — it answered the hub's last check (checked 16m ago). It answered 98% of checks over the last 30 days.
- Is figma-to-azure free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does figma-to-azure have?
- 9 tools: search-product-info, get-problems-solved, get-pricing, get-product-info, get-features, get-use-cases, get-workflow, get-comparisons, ….
- Is figma-to-azure safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99%· all time 99%
last good check
of 9 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get figma to azure plugin features
- get plugin pricing
- get setup workflow
- search product faqs
- takes → gives
- text → text
- tools
- 9 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get-problems-solved reads open 5h ago
Get the problems Figma to Azure solves — broken design handoffs, time wasted on manual processes, lost visual context, and design-dev miscommunication
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-pricing reads open 2h ago
Get Figma to Azure pricing plans including free work item details, monthly and yearly costs, and payment info
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-product-info reads open 2h ago
Get an overview of Figma to Azure — what it does, key stats, supported work item types, and data privacy info
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-features reads open 5h ago
Get the full list of Figma to Azure plugin features including automatic screenshots, work item creation, design versioning, custom fields, and enterprise auth
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-use-cases reads open 17h ago
Get specific use cases for the Figma to Azure plugin — user stories, bug reports, design system updates, multi-screen handoff, and more
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-workflow reads open 5h ago
Get step-by-step instructions for how to get, connect, and use the Figma to Azure plugin
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-comparisons reads open 17h ago
Compare Figma to Azure vs manual design handoff workflows and vs Zeplin — side-by-side feature and time comparisons
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget-faqs reads open 17h ago
Get frequently asked questions about Figma to Azure including setup, authentication, pricing, work item types, and data privacy
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessearch-product-info reads unknown 2h ago
Search across all Figma to Azure product information by keyword — searches features, FAQs, problems solved, use cases, pricing, and workflow
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Search keyword or question, e.g. 'screenshot', 'pricing', 'handoff', 'authentication', 'azure devops'" } } }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd91bb35f17bb2646.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d91bb35f17bb2646/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d91bb35f17bb2646?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.