Adobe MCP vs Figma MCP Server
A side-by-side look at the Adobe MCP and Figma MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Adobe MCP for architecture & design work as a local process; choose Figma MCP Server for architecture & design over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Adobe MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
ADOBE_MCP_APPS.
Choose Figma MCP Server when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
FIGMA_ACCESS_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 53/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | ADOBE_MCP_APPS | FIGMA_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 26 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Adobe MCP | View Figma MCP Server |
Tools & capabilities
Adobe MCP tools
No tool names declared yet. Check the project README from the listing page.
Figma MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Adobe MCP
{
"mcpServers": {
"adobe-mcp-2": {
"command": "npx",
"args": [
"-y",
"adobe-mcp-indesign"
],
"env": {
"ADOBE_MCP_APPS": "YOUR_ADOBE_MCP_APPS_HERE"
}
}
}
}
Figma MCP Server
{
"mcpServers": {
"figma-mcp-server-2": {
"url": "https://api.figma.com/v1/oauth/token"
}
}
}
Frequently asked questions
Adobe MCP is categorized under Architecture & Design and uses a local stdio subprocess. Figma MCP Server belongs to Architecture & Design and uses a remote HTTP/SSE transport. Pick Adobe MCP for architecture & design work and Figma MCP Server for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Adobe MCP is listed as free. Auth: no auth required. Figma MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add adobe-mcp-2 and figma-mcp-server-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Adobe MCP has a quality signal of 53/100 (Good) with 1 views, 0 installs and 26 GitHub stars. Figma MCP Server has 36/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.