Figma Context MCP vs Rcsb Pdb
A side-by-side look at the Figma Context MCP and Rcsb Pdb MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma Context MCP for architecture & design work as a local process; choose Rcsb Pdb for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIGMA_API_KEY, PORT. - You want tools like
get_figma_data, download_figma_images.
Choose Rcsb Pdb when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search, structure, polymer_entity.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Biology & Bioinformatics |
| Quality signal | 71/100 · Great | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | FIGMA_API_KEYPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16,064 | 0 |
| Directory activity | 10 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | 6 |
| Full listing | View Figma Context MCP | View Rcsb Pdb |
Tools & capabilities
Figma Context MCP tools 2
get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component informationdownload_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user
Rcsb Pdb tools 6
search"Find protein structure of [target]" / "search PDB for [protein]" / "is there a crystal structure of [X]" / "[disease target] structures" / "CRISPR / kinase / GPCR structures" — text search the RCSB PDB (the global archive of experimentally-determined 3D protein/RNA/DNA structures). Returns matching PDB IDs you can pass to `structure` or `summary`. Use for structural biology, drug design, protein characterization.structure"PDB entry [1abc] details" / "fetch protein structure [pdb_id]" / "metadata for [PDB ID]" — full PDB entry record by ID (e.g. "1abc", "7BV2"). Returns experimental method (X-ray / cryo-EM / NMR), resolution, authors, deposition date, organism, ligands, related entities. Use after `search` to inspect a specific structure.polymer_entity"Chain [N] of PDB [ID]" / "sequence of chain in [pdb_id]" — fetch the polymer-entity (protein/DNA/RNA chain) metadata for a specific PDB entry. Returns sequence, source organism, UniProt cross-references, GO annotations. Use to drill into one chain of a multi-chain structure.ligand"Ligand / cofactor / drug bound to [pdb_id]" / "small molecule in [PDB entry]" — fetch a non-polymer ligand record (small molecule, cofactor, ion, or bound drug) for a PDB entry. Use to inspect what's bound in a co-crystal structure — common in drug discovery / SBDD.assembly"Biological assembly of [pdb_id]" / "functional oligomer for [PDB entry]" — fetch a biological assembly record (the functional oligomeric unit, which often differs from the crystallographic asymmetric unit). Use when you need the actual functional form of a protein (dimer / tetramer / etc.) rather than the crystal contents.summaryLightweight lookup for a PDB entry by 4-char ID: tries the RCSB UniProt endpoint first, falls back to the core entry record. Returns title, experimental method, resolution, and deposition date without the full polymer/ligand detail of `structure`.
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.
Figma Context MCP
{
"mcpServers": {
"glips-figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Rcsb Pdb
{
"mcpServers": {
"rcsb-pdb": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-rcsb-pdb"
]
}
}
}
Frequently asked questions
Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. Rcsb Pdb belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Figma Context MCP for architecture & design work and Rcsb Pdb for biology & bioinformatics.
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.
Figma Context MCP is listed as free. Auth: api key required. Rcsb Pdb 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 glips-figma-context-mcp and rcsb-pdb as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figma Context MCP has a quality signal of 71/100 (Great) with 10 views, 0 installs and 16,064 GitHub stars. Rcsb Pdb has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.