Soma Nexus MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Figma personal access token for accessing Figma API. |
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 |
|---|---|
| get_figma_fileB | Fetch a Figma file. Prefer compact mode to avoid large payloads. |
| parse_figma_urlA | Parse a Figma URL and extract fileKey and nodeId. |
| validate_figma_to_code_indexA | Validate the global figma-to-code index and all per-component docs before generation. |
| get_figma_nodesB | Fetch specific Figma nodes, their subtrees, and optional geometry. |
| preview_figma_component_mappingB | Preview how a Figma node matches a Design System component via federated docs. |
| generate_flutter_component_from_figmaB | Generate a minimal Flutter widget snippet from a Figma node using federated docs mapping. |
| generate_flutter_page_from_figmaB | Generate Flutter page scaffold from a Figma page/frame URL, using DS components when matched. |
| get_figma_node_from_urlA | Fetch a specific Figma node directly from a full Figma URL. |
| get_figma_node_normalizedA | Fetch a Figma node from URL and return normalized metadata, tokens, styles, and asset refs. |
| get_figma_imagesB | Render Figma nodes to image URLs for assets and previews. |
| get_figma_componentsA | Fetch published components found in a Figma file. |
| get_figma_stylesC | Fetch published styles found in a Figma file. |
| get_figma_variablesB | Fetch local variables and collections from a Figma file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pablostefan/soma_nexus'
If you have feedback or need assistance with the MCP directory API, please join our Discord server