ScientificFigureLibrary
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ScientificFigureLibrarySearch for volcano plot templates in FigureYa"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Scientific Figure Library
Scientific Figure Library is a standard MCP server and MCP App for finding, importing, and materializing scientific figure references. It is not tied to Wisp: any stdio MCP host can use it. The included Wisp manifest and Skill are a thin optional adapter.
The first release has two template sources:
FigureYa — 319 searchable modules with local thumbnails and commit-pinned archives.
User Library — figures and plotting code copied from paths supplied by the MCP host.
The host Agent analyzes an uploaded image, a natural-language request, or a data file. It sends only compact visual/data profiles to the search tool, compares data compatibility before visual similarity, and materializes the selected reference for the next plotting step.
Safety contract
The server copies and extracts reference files but never executes plotting code or dependency installers. It verifies imported user files with SHA-256 and verifies FigureYa archives against the pinned catalog.
Materialization errors are terminal. figure_library_materialize returns a
STOP: error that instructs the Agent to report the exact failure and wait for
the user. The Agent must not switch extraction modes, use another downloader,
fetch the complete repository, recreate the template, or generate a
substitute/demo plot. This behavior is covered by the MCP smoke test.
Related MCP server: pubmed-search
Build
Requirements: Node.js 22 or newer.
npm install
npm run checkUse with any stdio MCP client
{
"mcpServers": {
"figure-library": {
"command": "node",
"args": ["/absolute/path/to/ScientificFigureLibrary/dist/index.js"],
"env": {
"FIGURE_LIBRARY_DIR": "/absolute/path/to/my-figure-library",
"FIGUREYA_SOURCE_PACK_DIR": "/optional/path/to/FigureYaSourcePack"
}
}
}
}FIGURE_LIBRARY_DIR defaults to ~/.figure-library. The server exposes:
figure_library_open— open an empty candidate workbench.figure_library_search— search FigureYa and/or the user library.figure_library_import— safely copy a user figure and/or code into the library.figure_library_source_status— inspect the user library and a FigureYa Source Pack.figure_library_describe— inspect one exact template.figure_library_materialize— write one selected reference to a project.
The MCP server does not contain a second model. For attachments, the host makes
files available locally and the Agent passes those paths to
figure_library_import. For search, the Agent passes compact descriptions, not
raw datasets.
Example import arguments:
{
"title": "Our lab volcano plot",
"description": "Labeled differential-expression volcano plot",
"tags": ["volcano", "differential expression"],
"visualProfile": "log2FC x-axis, -log10 FDR y-axis, labeled hits",
"dataProfile": "gene, log2FC, adjusted p value",
"imagePath": "/project/references/volcano.png",
"codePaths": ["/project/references/volcano.R"],
"license": "Internal lab reference"
}Supported visual references are PNG, JPEG, WebP, SVG, and PDF (20 MiB maximum). Up to 20 R, R Markdown, Quarto, Python, notebook, Julia, MATLAB, Markdown, TeX, shell, JSON, or YAML files may be imported (5 MiB each, 50 MiB total). Original absolute paths are never stored in the shareable manifest.
Distribution
The standalone npm tarball contains the server, App, FigureYa search catalog, and thumbnails, but not the large archive collection:
npm run package:npm
npm install --global ./release/scientific-figure-library-0.1.0.tgzUse scientific-figure-library as the MCP command after installation.
For Wisp:
npm run package:wispInstall release/scientific-figure-library-wisp-0.1.0.zip from Wisp
Settings → Plugins, enable it for a project, and start a fresh session.
FigureYa Source Pack
The core plugin and the optional Source Pack are deliberately separate. A Source Pack is an ordinary directory containing the existing per-module ZIPs from FigureYa-compressed:
FigureYaSourcePack/
├── FigureYa59volcanoV2.zip
└── archives/
└── FigureYa9heatmap.zipPass this directory as sourcePackDir or set
FIGUREYA_SOURCE_PACK_DIR. Resolution order is:
Local Source Pack.
Bases configured in
FIGUREYA_ARCHIVE_BASE_URLS.The commit-pinned FigureYa-compressed archive on GitHub.
The complete pinned archive collection is roughly 3 GiB, so it is not embedded in either plugin package. It can be copied by USB/shared storage or split into small transport packs:
npm run package:source-pack -- \
--source /path/to/FigureYa-compressed \
--name volcano \
--modules FigureYa59volcanoV2The helper verifies every selected ZIP and caps one transport pack at 200 MiB.
Extract the resulting
release/figure-library-source-pack-volcano-0.1.0.zip before use.
Materialized layouts
FigureYa template:
<destination>/<template-id>/
├── upstream/
├── TEMPLATE.md
└── template.lock.jsonUser template:
<destination>/<template-id>/
├── reference/
│ ├── preview.*
│ └── code/
├── TEMPLATE.md
└── template.lock.jsonAn existing target is never overwritten. Keep upstream/ or reference/
unchanged and adapt plotting code in a separate file.
Catalog development
The repository includes a generated FigureYa catalog. To regenerate it from local checkouts:
git -C /path/to/FigureYa-compressed ls-tree --name-only HEAD |
npm run catalog -- \
--source /path/to/FigureYa \
--figureya-commit <figureya-commit> \
--compressed-commit <compressed-repo-commit> \
--compressed-tree /path/to/compressed-github-tree.jsonLicense
Project code is MIT licensed. FigureYa-derived catalog data, thumbnails, and downloaded templates remain CC BY-NC-SA 4.0. User-imported material keeps the license supplied at import. See THIRD_PARTY_NOTICES.md.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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/xuzhougeng/ScientificFigureLibrary'
If you have feedback or need assistance with the MCP directory API, please join our Discord server