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 library 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 builds a compact retrieval intent, searches both sources, inspects the top preview, and decides whether that candidate actually matches before materializing anything. The catalog score orders retrieval candidates; it is not a recommendation or visual-similarity score.
For image input, the Agent must first inspect the user's image with the host's
view_image, then inspect the top candidate with figure_library_preview.
The final recommendation includes an Agent-produced visual pass/reject score
covering chart family, layout, axes/geometry, encodings, and annotations/style,
plus a separate data-compatibility verdict.
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",
"FIGURE_GALLERY_DIR": "/optional/path/to/my-personal-gallery",
"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, or validate and import a Figure Transfer Package. Direct-write mode remains for v0.2 compatibility; new Agents should use plan/apply.figure_library_plan_import— validate a direct import, calculate stable identity and component-level duplicate evidence, and write nothing.figure_library_apply_import— revalidate and apply one exact confirmed direct-import plan.figure_library_diff— validate one Transfer Package or Gallery entry and return a read-only create/update/unchanged diff.figure_library_upsert— explicitly apply a stable Transfer Package or Gallery create/update.figure_library_sync— validate or synchronize a Personal Gallery; dry-run is the default.figure_library_archive— logically archive any User Library entry bytemplateId, legacygalleryId, or adapter-scoped Registry source.figure_library_preview— return a candidate as MCP image content and, optionally, a checked project-local preview path for Agent inspection.figure_library_source_status— inspect effective User Library/Gallery paths, lifecycle counts, integrity counts, and a FigureYa Source Pack.figure_library_audit— read and verify manifests/files, legacy entries, and component-level duplicate evidence without writing.figure_library_reconcile— dry-run, apply, or roll back an explicitly approved logical duplicate archive using a write lock and recovery journal.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. Agent reasoning stays in the
host: understand input → build retrieval intent → search → view the top
candidate → visually and semantically audit it → materialize only an accepted
template. 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.
figure_library_preview returns standard MCP image content. In Wisp, pass an
absolute project-local destination (for example,
/project/.wisp/figure-library-previews) and call view_image on the returned
path. This keeps visual judgment with the Agent even when the host exposes only
the text portion of an MCP tool result.
Stable direct imports
For new direct imports, plan first:
{
"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",
"sourceKey": "manual:lab-volcano-v1",
"imagePath": "/project/references/volcano.png",
"codePaths": ["/project/references/volcano.R"],
"license": "Internal lab reference"
}sourceKey is optional, but recommended for an entry that should be updated in
place. It is a portable logical key: 1–200 lowercase ASCII letters, digits,
dot, underscore, colon, or hyphen. Never use a host path, URL with query data,
token, email, patient identifier, or other secret. Personal Gallery entries
must use gallery_id and Gallery sync rather than a direct sourceKey.
The plan returns action, confirmed title, proposed/existing templateId,
component fingerprints, matching templates, and planDigest, with
written: false. Present these fields, review status, and license to the user.
Only then call figure_library_apply_import with the same import fields plus:
{
"planDigest": "<64-hex plan digest>",
"expectedAction": "create",
"expectedTemplateId": "user-direct-<16-hex>",
"operationId": "lab-volcano-create-1"
}The apply step re-reads files and the User Library. A stale plan is rejected.
An exact create replay is safe. A duplicate_candidate requires an explicit
reuse or create_separate decision and reason; a source_conflict requires
an explicit replace_source reason. Template IDs never contain the raw
sourceKey and do not change when an existing stable source's title changes.
Without sourceKey, identity is content-addressed from the complete asset
fingerprint. Metadata can be revised for the same asset, but changing preview
or code intentionally produces a new-source candidate.
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.
Figure Transfer Package v1
figure_library_import accepts packagePath instead of the direct-import
fields. A v1 package is a ZIP containing exactly manifest.json and one figure
at the archive root:
figure-transfer-package.zip
├── manifest.json
└── figure.pngThe interoperable manifest contract is:
{
"schema": "figure-transfer-package.v1",
"version": 1,
"producer": { "name": "CiteBox", "version": "0.31.0" },
"exportedAt": "2026-08-01T01:02:03Z",
"source": {
"sourceId": "paper-42",
"figureId": "7",
"parentFigureId": null,
"figureLabel": "Fig 2",
"subfigureLabels": ["a", "b"],
"caption": "Original figure caption",
"page": 12,
"paper": {
"title": "Paper title",
"authors": ["First Author"],
"year": 2026,
"journal": "Journal name",
"doi": "10.1234/example",
"url": "https://example.org/paper"
},
"license": {
"scope": "article figure",
"text": "CC BY 4.0"
}
},
"figure": {
"file": "figure.png",
"mediaType": "image/png",
"bytes": 12345,
"sha256": "<64 lowercase-or-uppercase hex characters>"
}
}Unknown or unavailable provenance values must be represented explicitly with
an empty string, empty array, null, or "unknown" according to the field
type. IDs may be strings or non-negative integers. The importer rejects an
unsupported schema/version, unsafe or extra archive paths, oversized content,
extension/media-type/signature mismatch, byte-count mismatch, and SHA-256
mismatch. It stores the original manifest as read-only metadata and never
executes package content.
A Transfer Package enters the User Library as a draft visual_reference, so
default search does not present uncurated paper figures. Its stable producer +
source + figure identity makes repeated imports idempotent. If its content
changes, inspect it with figure_library_diff, then explicitly apply it with
figure_library_upsert.
Personal Gallery v1
The Gallery remains the editable source of truth; the User Library is a rebuildable search snapshot. A Gallery root contains entries like:
gallery/lab-volcano/
├── figure.yml
├── preview.png
├── description.md
├── source/
│ └── provenance.yml
└── code/
├── example.R
├── data_schema.yml
└── example.csvfigure.yml uses this schema:
schema: figure-library.gallery-entry.v1
gallery_id: lab-volcano
title: Lab volcano plot
tags: [volcano, differential expression]
visual_profile: log2FC x-axis, -log10 FDR y-axis, labeled hits
data_profile: gene, log2FC, adjusted p value
packages: [ggplot2]
license: Internal lab reference
asset_kind: plot_template # plot_template | visual_reference
language: R
plot_family: volcano
review_status: approved # draft | approved | archived
code_status: reviewed # none | scaffold | reviewed
preview: preview.png # optional default
description_file: description.md # optional default
provenance_file: source/provenance.yml # optional default
source_commit: 0123456789abcdef # optional; sync can also supply it
content_hash: <optional computed SHA-256>provenance.yml may contain producer, producer_version, exported_at,
source_id, figure_id, parent_figure_id, figure_label,
subfigure_labels, caption, paper_title, authors, year, journal,
doi, page, url, license_scope, and rights. The original description
and provenance files are retained in the snapshot. Gallery code/data files may
be R, R Markdown, Quarto, Python, notebook, Julia, MATLAB, shell, Markdown,
TeX, JSON, YAML, CSV, TSV, or text files; none are executed.
The importer computes content_hash from normalized searchable metadata,
provenance, and every stored file descriptor (file, bytes, SHA-256, and role),
with object keys and set-like tags/packages sorted; content_hash itself and
source_commit are excluded. If content_hash is present in figure.yml, it
must match. Stable gallery_id maps to one stable template ID and registry
record containing gallery_id, template_id, content_hash, and
source_commit.
Preview a complete sync without writing:
{
"galleryDirectory": "/absolute/path/to/gallery-repository",
"dryRun": true,
"sourceCommit": "0123456789abcdef"
}Set dryRun to false only after reviewing the returned per-field diffs.
Sync imports approved entries, skips drafts, and treats archived as a logical
archive rather than a deletion. Missing entries are never deleted implicitly.
Default search includes approved entries only; an explicit reviewStatus
filter can be used for review/audit. Search and sync also accept assetKind,
language, plotFamily, and codeStatus filters, keeping visual-only
references separate from reusable R templates.
Identity, management, audit, and reconcile
Every new Registry entry records an adapter-scoped logical source and versioned component fingerprints for preview, executable code, data, metadata, and the full asset. Component overlap is duplicate evidence only: equal previews or similar titles never trigger an automatic merge.
registry.contentHash remains the v0.2-compatible normalized source snapshot
hash. It is not the byte hash of the current template.json: local lifecycle
operations such as archive change review state without redefining the imported
source. Audit therefore calculates separate manifestSha256 and
verifiedFileSetDigest values from the current manifest and verified files.
Search and describe return a management object. Use its templateId as the
normal archive reference. registrySourceId is deliberately distinct from the
top-level search source (figureya or user). Gallery authority remains in
figure.yml; if a Gallery snapshot is locally archived while its Gallery entry
is still approved, the next sync will plan to restore the authoritative state.
Audit before any legacy cleanup:
{
"scope": "all",
"includeArchived": true
}Audit reports unreadable/invalid entries instead of silently omitting them, verifies every declared file, marks Registry-less legacy direct templates, and returns a duplicate evidence graph plus a deterministic recommendation only for the canonical ID.
figure_library_reconcile defaults to mode: "dry-run". Its expectedState
must copy the exact manifestSha256, verifiedFileSetDigest, and review status
from the reviewed audit. Apply only after backing up the complete User Library
and approving the exact canonical/duplicate IDs, hashes, and reason. Apply:
acquires the same User Library write lock as import/upsert/sync/archive;
archives only the named duplicate manifests;
retains every directory and reference file;
records a recovery journal and append-only alias ledger;
refuses stale state and incomplete prior transactions.
Rollback uses the same reconcileId and refuses to overwrite any later
manifest change. Never manually delete a lock, transaction directory, template
directory, or migration ledger until the interrupted state has been inspected.
If a dead process leaves prepared, committing, or rolling-back, first
verify that its recorded lock owner is no longer running and inspect the
journal. After the stale lock is deliberately cleared, rollback with the exact
same reconcile ID/canonical/duplicate IDs. Recovery accepts only manifests that
still equal that journal's before/after hashes and removes only a matching
partial apply ledger.
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.3.0.tgzUse scientific-figure-library as the MCP command after installation.
For Wisp:
npm run package:wispInstall release/scientific-figure-library-wisp-0.3.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.3.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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for searching research grants across NSF (US), ERC (EU), and KRF/NRF (Korea) via a unified interface. NIH excluded—covered by existing connectors.38MIT
- Alicense-qualityFmaintenanceMCP server for PubMed search and literature summarization52MIT
- AlicenseAqualityAmaintenanceComprehensive MCP server for academic research workflows, enabling paper searching across multiple sources, manuscript processing with citation placeholders, search caching, and citation export.11MIT
- Alicense-qualityDmaintenanceMCP server for AI-assisted research: paper ingestion, semantic search, citation graph traversal, cross-domain knowledge synthesis, and workflow automation.MIT
Related MCP Connectors
Auditable MCP server for PubMed, Europe PMC, ClinicalTrials.gov, and bioRxiv/medRxiv queries
MCP gateway federating 21 biomedical MCP servers behind one endpoint: gnomAD, ClinVar, HPO, VEP.
MCP server for Drosophila neuroscience data from VirtualFlyBrain
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