figma-console-mcp-autodocs

The materials explicitly state that no keys or environment variables are required, and there is no indication that API tokens, account credentials, or other sensitive authentication data must be provided, so credential exposure appears low.

Although the metadata declares no remote endpoints, the feature description mentions 'Obra Autodocs integration' and synchronizing/modifying Figma designs, which suggests possible real network interaction with external services or design platforms; due to the missing README, the actual data egress behavior and destinations cannot be verified from the materials.

The system checks indicate that this tool executes code; for an MCP tool, this typically means launching local processes and running its implementation logic. The materials do not show requests for system privileges beyond its stated purpose, so this is rated as caution based on normal execution capability.

The description explicitly says it can read, create, and modify Figma designs, synchronize design tokens bidirectionally, and auto-document components, indicating access to and modification of design data. This is consistent with its stated purpose, but the missing README leaves unclear whether it also reads/writes local files or accesses resources beyond expectations.

On the positive side, it is open-source under the MIT license and therefore auditable; however, it comes from a third-party registry, has 0 stars, unknown maintenance status, and almost no documentation, so supply-chain trust is limited and the source and dependencies should be reviewed before deployment.