MCP servers › io.github.irshadio › figmcp
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.irshadio/figmcp
Local Figma MCP server: frames to Flutter, React and HTML code, and design in Figma. No API limits. — the publisher's description
Summary
io.github.irshadio/figmcp is a local MCP server listed in the official MCP registry at version 1.6.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 15 tools, 0 resources and 3 prompts.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #2,446 of 15,112 packages by monthly downloads
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- local package
- Transport
- standard input/output
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 15
- Described as changing data
- 6 of 15 toolsAI-classified
- Mainly works on
- files and code on the machine it runs onAI-classified
- Topic
- media-and-designAI-classified
- Pricing
- freeAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 6 tools are described as changing something (add_code_connect_map, remove_code_connect_map, import_design_export, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.6.0, published 2026-10-19 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-14 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-10-14 to 2026-10-19; 2 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 2 versions
1.6.0· 2026-10-191.4.2· 2026-10-14
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.6.0 (published 2026-10-19).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.
6 of 15 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.
“Get design context for a Figma node — the primary tool for design-to-code workflows.”
Publisher declares: read-only yes · open-world no
13 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”frameworkstring“Code to generate: react, html or flutter.”clientLanguagesstring“Comma separated languages of the client, e.g.”clientFrameworksstring“Comma separated frameworks of the client, e.g.”screenboolean“Draw the node as a phone screen that fills the screen and scrolls when tall (default: portrait frames 300-480 wide).”pageboolean“React and HTML: draw the node as a web page that fills the viewport, never narrower than the design, with full-width sections stretching (default: frames 768 o…”assetsDirstring“Folder of the asset files in the code.”screenUtilboolean“Flutter: write lengths with flutter_screenutil (.w, .h, .r, .sp) so the layout scales from the design size (default: when the project's pubspec.yaml depends on…”excludeScreenshotboolean“Leave the screenshot out of the response.”forceCodeboolean“Always return code, even for very large nodes.”disableCodeConnectboolean“Draw mapped components from their layers instead of naming the code component.”skillNamesstring“Accepted for compatibility (logging only).”
“IMPORTANT: Always prefer to use get_design_context.”
Publisher declares: read-only yes · open-world no
2 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”
“Generate a screenshot for a given node or the currently selected node in Figma.”
Publisher declares: read-only yes · open-world no
5 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”maxDimensioninteger“Longest edge of the PNG in pixels (default 1024).”contentsOnlyboolean“Render the node in isolation, without overlapping content.”enableBase64Responseboolean“Also include the PNG inline as base64.”
“Get variable definitions for a given node id.”
Publisher declares: read-only yes · open-world no
2 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”
- download_assetsreads or searches
“Download assets for a single node: an exported render (`export`), the original images used as fills (`rawImages`, up to 20) and SVGs of the vector layers (`svgAssets`, up to 20).”
Publisher declares: read-only yes · open-world no
4 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”defaultFormatstringdefaultScalenumber
- get_code_connect_mapreads or searches
“Get the mapping from the component instances in a node to code components: { nodeId: { codeConnectName, codeConnectSrc, label } }, plus the components that are not mapped yet.”
Publisher declares: read-only yes · open-world no
2 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”
- add_code_connect_mapcreates or changes datadescribed as changing data
“Map a design component to a code component, so get_design_context names the code component for every instance of it.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
5 inputs, 3 required
nodeIdstringrequired“The ID of the node, eg.”fileKeystring“The key of the Figma file.”componentNamestringrequired“Code component name, e.g.”sourcestringrequired“Path of the code component in the project.”labelstring“Framework, e.g.”
- remove_code_connect_mapdeletesdescribed as changing data
“Remove the code component mapping saved by add_code_connect_map, so get_design_context stops naming that code component.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 1 required
nodeIdstringrequired“The ID of the node, eg.”fileKeystring“The key of the Figma file.”
“Status of the local Figma connection: whether the plugin is connected, the pairing code it needs, the open file, page and selection, the project and its Code Connect file, and the saved snapshots.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
- import_design_exportcreates or changes datadescribed as changing data
“Save a design export JSON (frames with node trees, as the plugin produces) as a snapshot, so its nodes can be read without the plugin.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
pathstringrequired“Absolute path of the export JSON file.”
- save_design_exportcreates or changes datadescribed as changing data
“Write a full design export of a node (default: the selection) to a JSON file: the node tree with every layout, paint, text, variable, style, component and interaction detail, icon SVGs, renders of ma…”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
3 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”pathstring“Absolute .json path to write (default: the data folder).”
“Create or edit designs in the file open in Figma Desktop by running JavaScript against the Figma plugin API.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 1 required
codestringrequired“Body of an async function run with `figma` in scope.”fileKeystring“The key of the Figma file.”timeoutMsinteger“How long to wait for the script, in ms (default 60000).”
Show 3 more tools
“Put an image file from this computer into the file open in Figma Desktop: a PNG, JPG or GIF becomes a rectangle with the image fill (or the fill of the layer `nodeId`), and an SVG becomes editable ve…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
11 inputs, 1 required
pathstringrequired“Path of the image file (absolute, or relative to the project).”nodeIdstring“Set the image as the fill of this layer instead of making a new one (not for SVG).”parentIdstring“Frame or group to put the new layer in.”namestring“Layer name (default: the file name).”xnumberynumberwidthnumberheightnumberscaleModestring“How the image fills the layer (default FILL).”keepFillsboolean“With nodeId: add the image above the existing fills instead of replacing them.”fileKeystring“The key of the Figma file.”
- verify_codeon 3 other servers
“Check Flutter or React + Tailwind code against the design: renders it at 2x (Flutter with `flutter test`, React in headless Chrome with Tailwind) and compares the render with Figma's own 2x render of…”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
12 inputs
nodeIdstring“The ID of the node, eg.”fileKeystring“The key of the Figma file.”frameworkstring“flutter or react (default: from the file, else as get_design_context picks: the client, then the project).”clientLanguagesstring“Comma separated languages of the client, e.g.”clientFrameworksstring“Comma separated frameworks of the client, e.g.”filestring“Flutter: the .dart file with the widget, under the project's lib/.”widgetstring“Flutter: the widget class in `file` (default: its first widget class).”cssstring“React: a CSS file to load with the component, e.g.”tailwindnumber“React: the Tailwind major version (default: the project's, else 4).”viewportstring“Lay the code out on a screen of this size, e.g.”fontsarray“Folders with font files (default: the project's assets/fonts and the system fonts).”flutterstring“Path of the flutter tool, when it is not on PATH.”
- search_design_systemreads or searches
“Search the design system of the file open in Figma Desktop: local components and component sets (with their properties and variant options), library components the file already uses (with an instance…”
Publisher declares: read-only yes · open-world no
5 inputs
querystring“Words to look for, e.g.”kindsarray“What to search (default: all of components, styles, variables).”allPagesboolean“Search components on every page, not just the current one (slower on large files).”limitinteger“Most results per kind (default 50).”fileKeystring“The key of the Figma file.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 15 tools
- Says what it returns
- 80% of 15 tools
- States limits, defaults or errors
- 20% of 15 tools
- Says when to use it
- 100% of 15 tools
- Items covered per tool
- 3.0 of 4 on average
Counted from the listing
- Parameters with a description
- 91% of 70
- Tools with a description
- 100% of 15
- Typical description length
- 576 characters
The tool set
Counted from the listing
- Tools
- 15
- Size of the list
- about 5,929 tokens for an agent to load (characters ÷ 4)
- Naming
- 14 of 15 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 15 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package @irshad.io/figma-local-mcp
Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"figmcp": {
"command": "npx",
"args": [
"-y",
"@irshad.io/figma-local-mcp@1.6.0"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"figmcp": {
"command": "npx",
"args": [
"-y",
"@irshad.io/figma-local-mcp@1.6.0"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"figmcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@irshad.io/figma-local-mcp@1.6.0"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"figmcp","type":"stdio","command":"npx","args":["-y","@irshad.io/figma-local-mcp@1.6.0"]}'Claude Code
claude mcp add --transport stdio figmcp -- npx -y @irshad.io/figma-local-mcp@1.6.0
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @irshad.io/figma-local-mcp@1.6.0
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 1.6.0
- Latest stable
- 1.6.0
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-CFca9D68SV2gpHgG0…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-10-23.
Usage
- Downloads
- 1,067 in the last month
Source: api.npmjs.org · 2026-10-23.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Published package can be started | Started and answered | matches | our test · 2026-10-23 |
| Version 1.6.0 on npm | Exists and can be installed | matches | npm · 2026-10-23 |
| Repository github.com/irshadio/figmcp | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.irshadio
- GitHub owner
- a personal account (irshadio)
- Build record
- signed
- Repository
- github.com/irshadio/figmcp
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- #2,446 of 15,112 packages by monthly downloads
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.irshadio/figmcp
Answered from the data aboveIs io.github.irshadio/figmcp safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 6 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Is io.github.irshadio/figmcp free to use?
Its website (figmcp.web.app/) describes a free pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.
Has io.github.irshadio/figmcp been security tested?
Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.
What can io.github.irshadio/figmcp do?
It lists 15 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and run code or commands. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.irshadio/figmcp change or delete data?
6 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.irshadio/figmcp publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 1.6.0, the latest stable release on npm.
Where is the source code of io.github.irshadio/figmcp?
In github.com/irshadio/figmcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.leancoderkavy/premiere-proMCP for Adobe Premiere Proalso has tools that creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
- io.github.kvoltmer/audionautAudionautalso has tools that creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
- io.github.KyaniteLabs/kinocutKinocutalso has tools that creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
- io.github.KyaniteLabs/mcp-videomcp-videoalso has tools that creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
- tech.kyanitelabs/kinocutKinocutalso has tools that creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
- io.github.awv-informatik/classcadClassCADalso has tools that creates or changes data, deletes, runs code or commands, reads or searchescompare with this one
Active servers whose topic is also “media-and-design” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (read-only run)
We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: exercised
- Fake assistant turns: exercised
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
4 exercised9 not run (reason given)5 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 12Hidden content
audience-hidingChecks resources that hide content from the user.exercised - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted the published package in an isolated sandbox (read-only mode)
- 11,104 msConnected after 0 redirects.
- Read the inventory: 15 tools, 0 resources, 3 prompts.
- 21,817 msFinished: 4 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Is it free? Yes. The server and the plugin are free to use, with no usage limits and no account to create.”
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.irshadio/figmcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.irshadio/figmcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.irshadio/figmcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology