com.mcparmory/figma
OCI · GHCR.IO/MCPARMORY/FIGMA:1.0.6 · 2 COMPONENTS · SCANNED SEP 20
Export files, access design data, manage projects, comments, and team assets
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4596 tokens (~112/item across 41 items; 41 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 41 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/figma MCP server?
com.mcparmory/figma runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/figma:1.0.6. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/figma:1.0.6
claude mcp add com-mcparmory-figma -- docker run --rm -i ghcr.io/mcparmory/figma:1.0.6
{
"mcpServers": {
"com-mcparmory-figma": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/figma:1.0.6"
]
}
}
} {
"servers": {
"com-mcparmory-figma": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/figma:1.0.6"
]
}
}
} codex mcp add com-mcparmory-figma -- docker run --rm -i ghcr.io/mcparmory/figma:1.0.6
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-figma": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/figma:1.0.6"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-figma:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/figma:1.0.6"] {
"McpServers": {
"com-mcparmory-figma": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/figma:1.0.6"
]
}
}
} {
"mcpServers": {
"com-mcparmory-figma": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/figma:1.0.6"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/figma:1.0.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_comment_reaction Add Comment Reaction ~130
Add an emoji reaction to a file comment. Reactions allow users to quickly respond to comments with emoji expressions.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique identifier of the comment to react to. |
| emoji | string | yes | The emoji reaction as a shortcode format. Supports optional skin tone modifiers for applicable emoji. Valid shortcodes are defined in the emoji-mart native set. |
| file_key | string | yes | The file identifier to add the reaction to. Can be a file key or branch key; use GET /v1/files/:key with the branch_data query parameter to retrieve a branch key. |
No output schema declared.
No examples provided.
add_file_comment Add File Comment ~150
Posts a new comment on a file or replies to an existing root comment. Use the comment_id parameter to reply to a specific comment.
| Name | Type | Req | Description |
|---|---|---|---|
| client_meta | – | – | Metadata specifying the position or location where the comment should be placed within the file. |
| comment_id | string | – | The ID of the root comment to reply to. Replies to replies are not supported; only root-level comments can be replied to. |
| file_key | string | yes | The file identifier to add the comment to. Can be a file key or branch key; use GET /v1/files/:key with the branch_data query parameter to retrieve a branch key. |
| message | string | yes | The text content of the comment to post. |
No output schema declared.
No examples provided.
bulk_modify_variables Bulk Modify Variables ~275
Bulk create, update, and delete variables, variable collections, modes, and mode values in a file. Changes are applied atomically in a defined order: collections, then modes, then variables, then mode values.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The file to modify variables in. Can be a file key or branch key obtained from GET /v1/files/:key with the branch_data query parameter. |
| variableCollections | array | – | Array of variable collection objects to create, update, or delete. Each object must include an action property (create, update, or delete). Processed first in the request. |
| variableModeValues | array | – | Array of variable mode value assignments to set specific values for variables under particular modes. Variables cannot be aliased to themselves or form alias cycles. Processed last in the request. |
| variableModes | array | – | Array of variable mode objects to create, update, or delete within collections. Each collection supports a maximum of 40 modes with names up to 40 characters. Processed second in the request. |
| variables | array | – | Array of variable objects to create, update, or delete. Each collection supports a maximum of 5000 variables. Variable names must be unique within a collection and cannot contain special characters s… |
No output schema declared.
No examples provided.
create_dev_resources Create Dev Resources ~87
Bulk create dev resources across multiple files. Successfully created resources are returned in the links_created array, while any resources that fail validation appear in the errors array with failure reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| dev_resources | array | yes | An array of dev resource objects to create. Each resource must reference a valid file_key, have a unique URL per node, and not exceed the 10 dev resource limit per node. |
No output schema declared.
No examples provided.
delete_comment Delete Comment ~82
Deletes a specific comment from a file. Only the comment author is permitted to delete their own comments.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique identifier of the comment to delete. |
| file_key | string | yes | The file or branch key identifying the file containing the comment. Retrieve the branch key using GET /v1/files/:key with the branch_data query parameter. |
No output schema declared.
No examples provided.
export_file_json Export File as JSON ~273
Export a Figma file as JSON, including document structure, components, and optional metadata. Supports partial exports by node ID and configurable depth traversal.
| Name | Type | Req | Description |
|---|---|---|---|
| branch_data | boolean | – | Include branch metadata in the response, showing the main file key if this is a branch, or branch metadata if the file has branches. |
| depth | number | – | Controls traversal depth into the document tree. A value of 1 returns only pages; 2 returns pages and top-level objects; omitting returns the entire tree. |
| file_key | string | yes | The unique identifier of the file to export. Can be extracted from the Figma file URL (https://www.figma.com/file/{file_key}/{title}) or obtained as a branch key using the branch_data parameter. |
| geometry | string | – | Set to include vector path data in the export for shape and vector nodes. |
| ids | string | – | Comma-separated list of node IDs to include in the export. When specified, returns only the requested nodes, their children, and ancestor chains. Top-level canvas nodes are always included regardless… |
| plugin_data | string | – | Comma-separated list of plugin IDs and/or the string 'shared' to include plugin data written to the document. Plugin data will appear in pluginData and sharedPluginData properties. |
No output schema declared.
No examples provided.
get_component Get Component ~51
Retrieve detailed metadata for a specific component using its unique identifier. This operation returns comprehensive information about the component's configuration and properties.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The unique identifier that uniquely identifies the component within the system. |
No output schema declared.
No examples provided.
get_component_set Get Component Set ~50
Retrieve metadata for a published component set using its unique identifier. Returns detailed information about the component set configuration and properties.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The unique identifier that uniquely identifies the component set to retrieve. |
No output schema declared.
No examples provided.
get_current_user Get Current User ~28
Retrieve the profile and account information for the currently authenticated user. This endpoint requires valid authentication credentials.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_file_metadata Get File Metadata ~63
Retrieve metadata for a file or branch. Provide either a file key or branch key to access file information.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The unique identifier for the file or branch. Use a file key for standard file metadata or a branch key for branch-specific metadata. |
No output schema declared.
No examples provided.
get_file_nodes Get File Nodes ~242
Retrieve specific nodes from a Figma file as JSON objects. Extract node data by providing node IDs, with optional support for vector geometry, nested traversal depth, and plugin data.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | number | – | How many levels deep to traverse the node tree from each specified node. A value of 1 returns only direct children; omitting this parameter returns the entire subtree. |
| file_key | string | yes | The Figma file identifier to query. Can be either a file key or branch key (obtain branch key via GET /v1/files/:key with branch_data parameter). |
| geometry | string | – | Include vector path data in the response. Set to 'paths' to export vector geometry; omit to exclude vector data. |
| ids | string | yes | Comma-separated list of node IDs to retrieve. The API will return data for each specified node, though some values may be null if a node ID does not exist in the file. |
| plugin_data | string | – | Comma-separated list of plugin IDs and/or the string 'shared' to include plugin data written to the document. Plugin data will be returned in pluginData and sharedPluginData properties. |
No output schema declared.
No examples provided.
get_style Get Style ~46
Retrieve detailed metadata for a specific style using its unique identifier. Use this to fetch style configuration and properties.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The unique identifier that references the specific style to retrieve. |
No output schema declared.
No examples provided.
get_webhook Get Webhook ~51
Retrieve a webhook configuration by its ID. Use this to fetch details about a specific webhook including its URL, events, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The unique identifier of the webhook to retrieve. |
No output schema declared.
No examples provided.
list_activity_logs List Activity Logs ~181
Retrieve a list of activity log events filtered by type, time range, and ordering. Useful for auditing, monitoring system changes, and tracking user actions.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | number | – | Unix timestamp marking the end of the time range (inclusive). Defaults to the current timestamp if unspecified. |
| events | string | – | Filter results to include only specified event types. Accepts comma-separated values to include multiple event types; all events are returned if unspecified. |
| limit | number | – | Maximum number of events to return in the response. Defaults to 1000 if unspecified. |
| order | string | – | Sort order for events by timestamp. Use ascending order to show oldest events first, or descending order to show newest events first. |
| start_time | number | – | Unix timestamp marking the start of the time range (inclusive). Defaults to one year ago if unspecified. |
No output schema declared.
No examples provided.
list_comment_reactions List Comment Reactions ~108
Retrieves a paginated list of reactions left on a specific comment. Use this to see all emoji reactions and their authors for a given comment.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique identifier of the comment to retrieve reactions from. |
| file_key | string | yes | The file identifier to retrieve the comment from. Can be either a file key or branch key; use `GET /v1/files/:key` with the `branch_data` query parameter to obtain a branch key if needed. |
No output schema declared.
No examples provided.
list_component_sets List Component Sets ~80
Retrieve a paginated list of published component sets available in a team's library. Use pagination to manage large result sets efficiently.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | number | – | The number of component sets to return per page. Useful for controlling response size and implementing pagination. |
| team_id | string | yes | The unique identifier of the team whose component sets you want to retrieve. |
No output schema declared.
No examples provided.
list_component_sets_file List Component Sets in File ~68
Retrieve all published component sets available in a file library. This operation requires a main file key and cannot be used with branch keys.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The main file key identifying the library file. Branch keys are not supported as component sets can only be published from main files. |
No output schema declared.
No examples provided.
list_dev_resources List Dev Resources ~93
Retrieve development resources associated with a file. Optionally filter results to specific nodes within the file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The main file key to retrieve dev resources from. Branch keys are not supported. |
| node_ids | string | – | Comma-separated list of node identifiers to filter results. When specified, only dev resources attached to these nodes are returned. Omit to retrieve all dev resources in the file. |
No output schema declared.
No examples provided.
list_file_comments List File Comments ~108
Retrieves all comments left on a file. Supports both file keys and branch keys for accessing comments across different file versions.
| Name | Type | Req | Description |
|---|---|---|---|
| as_md | boolean | – | When enabled, converts comments to their markdown equivalents where applicable for better formatting compatibility. |
| file_key | string | yes | The file or branch identifier to retrieve comments from. Use the file key for the main file, or obtain a branch key via GET /v1/files/:key with the branch_data query parameter to access comments on a… |
No output schema declared.
No examples provided.
list_file_components List File Components ~66
Retrieve a list of published components available in a file library. Only main file keys are supported, as components cannot be published from branch files.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The main file key identifying the file library to retrieve components from. Branch keys are not supported for this operation. |
No output schema declared.
No examples provided.
list_file_styles List File Styles ~66
Retrieve a list of published styles available in a file library. Styles can only be published from main files, not from branches.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The main file key containing the styles to retrieve. Branch keys are not supported since style publishing is only available for main files. |
No output schema declared.
No examples provided.
list_file_versions List File Versions ~103
Retrieve the version history of a file to see how it has evolved over time. Use the returned version information to render a specific version via another endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The file or branch key identifying which file's version history to retrieve. Obtain the branch key using GET /v1/files/:key with the branch_data query parameter. |
| page_size | number | – | Number of version records to return per page. Defaults to 30 if not specified. |
No output schema declared.
No examples provided.
list_image_fills List Image Fills ~99
Retrieve download URLs for all images used in image fills within a Figma document. Image URLs are valid for up to 14 days and can be located by their imageRef attribute in Paint objects from the file endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The Figma file identifier to retrieve images from. Accepts either a file key or branch key; use GET /v1/files/:key with branch_data query parameter to obtain a branch key. |
No output schema declared.
No examples provided.
list_library_component_actions List Library Component Actions ~181
Retrieve analytics data for component actions within a library, aggregated by the specified dimension (component or team). Use this to analyze usage patterns and activity metrics across your design library.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | The latest week to include in the analytics results, specified as an ISO 8601 date. The date will be rounded forward to the nearest end of a week. Defaults to the most recently computed week. |
| file_key | string | yes | The unique identifier of the library file for which to retrieve analytics data. |
| group_by | string | yes | The dimension by which to aggregate the returned analytics data. |
| start_date | string | – | The earliest week to include in the analytics results, specified as an ISO 8601 date. The date will be rounded back to the nearest start of a week. Defaults to one year prior to the end date. |
No output schema declared.
No examples provided.
list_library_component_usages List Library Component Usages ~77
Retrieves analytics data on how components from a library are being used, with results grouped by the specified dimension (component or file).
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The unique identifier of the library file for which to retrieve component usage analytics. |
| group_by | string | yes | The dimension by which to group the returned usage analytics data. |
No output schema declared.
No examples provided.
list_library_style_actions List Library Style Actions ~186
Retrieve analytics data for style actions in a library, aggregated by the specified dimension (style or team). Use date parameters to filter results to a specific time range.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | The latest week to include in results, specified as an ISO 8601 date. The date will be rounded forward to the nearest week end. Defaults to the most recently computed week. |
| file_key | string | yes | The unique identifier of the library for which to fetch style action analytics. |
| group_by | string | yes | The dimension to group analytics results by. Choose 'style' to aggregate by individual styles or 'team' to aggregate by team. |
| start_date | string | – | The earliest week to include in results, specified as an ISO 8601 date. The date will be rounded back to the nearest week start. Defaults to one year prior to the end date. |
No output schema declared.
No examples provided.
list_library_style_usages List Library Style Usages ~117
Retrieves analytics data on how styles are used within a library, aggregated by the specified dimension (style or file). Use this to understand style adoption and usage patterns across your design library.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The unique identifier of the library file for which to retrieve style usage analytics. |
| group_by | string | yes | The dimension by which to group the returned analytics data. Choose 'style' to see usage broken down by individual styles, or 'file' to see usage broken down by the files that consume those styles. |
No output schema declared.
No examples provided.
list_library_variable_actions List Library Variable Actions ~158
Retrieve analytics data for variable actions within a library, aggregated by the specified dimension (variable or team). Use date parameters to filter results to a specific time range.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | ISO 8601 date marking the end of the analytics period. Dates are rounded forward to the nearest week end. Defaults to the latest computed week. |
| file_key | string | yes | The unique identifier of the library for which to fetch variable action analytics. |
| group_by | string | yes | The dimension by which to group the returned analytics data. |
| start_date | string | – | ISO 8601 date marking the start of the analytics period. Dates are rounded back to the nearest week start. Defaults to one year prior to the end date. |
No output schema declared.
No examples provided.
list_library_variable_usages List Library Variable Usages ~104
Retrieves analytics data on how variables are used within a library, aggregated by the specified dimension (variable or file). Use this to understand variable usage patterns and dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The unique identifier of the library file for which to retrieve variable usage analytics. |
| group_by | string | yes | The dimension by which to aggregate the returned variable usage data. Choose 'variable' to group by individual variables, or 'file' to group by source files. |
No output schema declared.
No examples provided.
list_local_variables List Local Variables ~86
Retrieve all local variables created in a file and remote variables referenced within it. This operation is restricted to full members of Enterprise organizations and supports examining variable modes and bound variable details.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The file or branch identifier to retrieve variables from. Use the branch key obtained from GET /v1/files/:key with the branch_data query parameter to access branch-specific variables. |
No output schema declared.
No examples provided.
list_payments List Payments ~222
Retrieve payment information for a user on a specific Community file, plugin, or widget. You can only query resources that you own.
| Name | Type | Req | Description |
|---|---|---|---|
| community_file_id | string | – | The ID of the Community file to query. Find this in the file's Community page URL (the number after 'file/'). Provide exactly one of: community_file_id, plugin_id, or widget_id. |
| plugin_id | string | – | The ID of the plugin to query. Find this in the plugin's manifest or Community page URL (the number after 'plugin/'). Provide exactly one of: community_file_id, plugin_id, or widget_id. |
| user_id | string | – | The ID of the user whose payment information you want to retrieve. Obtain this by having the user authenticate via OAuth2 to the Figma REST API. |
| widget_id | string | – | The ID of the widget to query. Find this in the widget's manifest or Community page URL (the number after 'widget/'). Provide exactly one of: community_file_id, plugin_id, or widget_id. |
No output schema declared.
No examples provided.
list_project_files List Project Files ~71
Retrieve all files within a specified project. Optionally include branch metadata for files that contain branches.
| Name | Type | Req | Description |
|---|---|---|---|
| branch_data | boolean | – | Include branch metadata in the response for each main file that contains branches within the project. |
| project_id | string | yes | The unique identifier of the project from which to retrieve files. |
No output schema declared.
No examples provided.
list_published_variables List Published Variables ~66
Retrieve all variables published from a file, including their subscription IDs and last published timestamps. Available only to full members of Enterprise organizations.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The main file key to retrieve published variables from. Branch keys are not supported as variables cannot be published from branches. |
No output schema declared.
No examples provided.
list_team_components List Team Components ~85
Retrieve a paginated list of published components available in a team's component library. Use pagination to manage large result sets efficiently.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | number | – | The number of components to return per page. Specify a value between 1 and 1000 to control result set size. |
| team_id | string | yes | The unique identifier of the team whose components you want to list. |
No output schema declared.
No examples provided.
list_team_projects List Team Projects ~77
Retrieve all projects within a specified team that are visible to the authenticated user. Only projects accessible to the token owner or authenticated user will be returned.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | The unique identifier of the team. You can find the team ID in the URL of your team page, positioned after 'team' and before your team name. |
No output schema declared.
No examples provided.
list_team_styles List Team Styles ~80
Retrieve a paginated list of published styles from a team's design library. Use pagination to control the number of results returned per request.
| Name | Type | Req | Description |
|---|---|---|---|
| page_size | number | – | The number of styles to return per page. Adjust this value to control result set size. |
| team_id | string | yes | The unique identifier of the team whose styles you want to retrieve. |
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~116
Retrieve webhooks filtered by context or plan. Use context_id to get webhooks for a specific context, or plan_api_id to retrieve all webhooks across all accessible contexts with pagination support.
| Name | Type | Req | Description |
|---|---|---|---|
| context_id | string | – | The unique identifier of the context to retrieve webhooks for. Cannot be used together with plan_api_id. |
| plan_api_id | string | – | The unique identifier of your plan to retrieve all webhooks across all accessible contexts. Cannot be used together with context_id. Results are paginated when using this parameter. |
No output schema declared.
No examples provided.
remove_comment_reaction Remove Comment Reaction ~109
Remove a reaction from a comment. Only the user who added the reaction can delete it.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique identifier of the comment from which to remove the reaction. |
| emoji | string | yes | The emoji reaction to remove, specified as a shortcode format. Skin tone modifiers are supported where applicable. |
| file_key | string | yes | The file or branch key containing the comment. Retrieve the branch key using GET /v1/files/:key with the branch_data query parameter. |
No output schema declared.
No examples provided.
remove_dev_resource Remove Dev Resource ~78
Remove a dev resource from a file. This operation permanently deletes the specified dev resource and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| dev_resource_id | string | yes | The unique identifier of the dev resource to delete. |
| file_key | string | yes | The main file key containing the dev resource to delete. Must be a main file key, not a branch key. |
No output schema declared.
No examples provided.
render_node_images Render Node Images ~201
Render images from specified nodes in a file. Returns a map of node IDs to image URLs, with null values indicating failed renders. Rendered images expire after 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | The file to export images from. Accepts either a file key or branch key. Use GET /v1/files/:key with the branch_data query parameter to retrieve a branch key. |
| format | string | – | Output format for the rendered image. |
| ids | string | yes | Comma-separated list of node IDs to render. Multiple node IDs can be specified to render multiple images from the same file. |
| scale | number | – | Scaling factor for the rendered image. Values between 0.01 and 4 are supported, where 1.0 represents the original size. |
| svg_include_id | boolean | – | Whether to include id attributes for all SVG elements. When enabled, adds the layer name to the id attribute of each SVG element. |
No output schema declared.
No examples provided.
update_dev_resources Update Dev Resources ~82
Bulk update dev resources across multiple files. Successfully updated resource IDs are returned in the response, while any resources that fail to update are included in an errors array.
| Name | Type | Req | Description |
|---|---|---|---|
| dev_resources | array | yes | An array of dev resource objects to update. Each resource in the array will be processed, and results will be returned indicating which resources were successfully updated and which encountered error… |
No output schema declared.
No examples provided.
What is the com.mcparmory/figma MCP server?
com.mcparmory/figma is an MCP server listed in the public MCP registry as com.mcparmory/figma. Export files, access design data, manage projects, comments, and team assets. This page covers its container image (ghcr.io/mcparmory/figma:1.0.6).
Is the com.mcparmory/figma MCP server safe to use?
com.mcparmory/figma scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/figma MCP server expose?
com.mcparmory/figma exposes 41 tools: export_file_json, get_file_nodes, render_node_images, list_image_fills, get_file_metadata, and 36 more. Their descriptions and schemas cost roughly 4,596 tokens of context every time the server is loaded.
Is the com.mcparmory/figma MCP server still maintained?
com.mcparmory/figma is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.