scaps-mcp
MCP server for SCAPS-1D, the one-dimensional solar cell simulator of the University of Gent. It drives your own SCAPS installation headless and gives any MCP client device design, simulation, batches, curve fitting, result analysis and realism checks.
SCAPS is not included. Request it from its authors as described on the SCAPS website and follow their conditions of use, which include citing SCAPS in publications.
Capabilities
- Devices: describe any
.def, edit it with every SCAPSsetcommand, load.materialfiles into layers, create devices from scratch (up to 7 layers, 7 defects per layer, 3 defects per interface), and set solver numerics that scripts cannot reach. - Simulation: J-V, QE, C-V and C-f with any working point, illumination side, spectrum or generation model, ND filter and cut-off; energy band, generation-recombination and AC profiles.
- Batches: grid or paired sweeps over any
setoractionkey, including temperature, intensity and bias. - Fitting and optimisation: bounded Nelder-Mead against one or several measured curves (light and dark J-V, QE, C-V), or towards maximum, minimum or target efficiency, Voc, Jsc or FF.
- Input files: import shared
.def,.material, absorption, spectrum, generation, filter, grading and measurement files, or write them from data with unit conversion (absorption from alpha or extinction coefficient k). - Analysis: Shockley-Queisser limit of the absorber under the spectrum used, QE-integrated Jsc, Mott-Schottky built-in voltage and doping, band offsets at every interface.
- Realism checks: results above the detailed-balance limit, missing radiative recombination, ideal interfaces, band spikes and cliffs, compensating defects, implausible densities of states, default absorption models and other common causes of unphysical SCAPS studies.
- Jobs: long runs continue in the background with progress, waiting and cancellation.
- Validation: every key and value is checked against the command list of the installed SCAPS version before SCAPS starts.
Requirements
- SCAPS-1D 3.3 (tested with 3.3.12)
- Python 3.11 or newer
Setup on Windows
Install SCAPS with its installer into a folder you can write to. SCAPS uses its installation folder as its working folder, and its authors advise against Program Files. Copy any SCAPS update files over the installed ones and check that the server finds it:
uvx scaps-mcp doctor
Setup on Linux (optional)
SCAPS is a Windows program; on Linux it runs headless under Wine and Xvfb. Install both (Debian and Ubuntu):
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install wine wine32:i386 xvfb
Create a 32-bit prefix and install SCAPS into it, from the folder holding the unpacked SCAPS installer:
export WINEARCH=win32 WINEPREFIX="$HOME/scaps/prefix"
xvfb-run -a bash -c 'wineboot -i && wineserver -w'
xvfb-run -a bash -c 'wine setup.exe /q /AcceptLicenses yes /r:n && wineserver -w'
Copy any SCAPS update files over the installed ones and check that the server finds it:
uvx scaps-mcp doctor
Finding SCAPS
Without SCAPS_HOME, the server looks for a folder holding scapsXXXX.exe with its def, results and script folders, in folders whose name contains "scaps", one or two levels below:
- Windows: the system drive, your user folder, Documents, Desktop, Downloads, Program Files and Program Files (x86).
- Linux: your home folder and the
drive_candProgram Filesfolders of Wine prefixes:~/.wine,$WINEPREFIX,$SCAPS_WINEPREFIX, winetricks prefixes and prefixes inside home folders named likescaps.
When several installations are found, the newest SCAPS version is used. scaps_status and doctor show the folder in use and any others. Set SCAPS_HOME to choose one yourself.
Configuration
| Variable | Meaning | Default |
|---|---|---|
SCAPS_HOME |
SCAPS folder containing scapsXXXX.exe |
found automatically |
SCAPS_EXE |
executable name | newest scaps*.exe |
SCAPS_TIMEOUT |
seconds per SCAPS run | 300 |
SCAPS_RUNS_DIR |
where run inputs and results are kept | user cache folder |
SCAPS_WINEPREFIX |
Linux only: Wine prefix | the prefix containing the SCAPS folder |
SCAPS_WINE, SCAPS_WINESERVER |
Linux only: Wine binaries | found on the system |
SCAPS_XVFB |
Linux only: 0 to use the current display instead of Xvfb |
1 |
Plots need the optional extra: uvx --with matplotlib scaps-mcp, or install scaps-mcp[plot].
Clients
Claude Code:
claude mcp add --transport stdio scaps -- uvx scaps-mcp
Straight from the repository instead of PyPI:
claude mcp add --transport stdio scaps -- uvx --from git+https://github.com/asiff00/scaps-mcp scaps-mcp
Add --env SCAPS_HOME=<folder> before scaps when SCAPS is somewhere the server does not search.
Project configuration (.mcp.json), with a long tool timeout for batches and fits:
{
"mcpServers": {
"scaps": {
"command": "uvx",
"args": ["scaps-mcp"],
"timeout": 3600000
}
}
}
Other MCP clients start the same command, with SCAPS_HOME in the server environment only when SCAPS is somewhere the server does not search.
Tools
| Tool | Purpose |
|---|---|
scaps_status |
Installation, version, run folder, plotting support, running jobs |
scaps_list_files |
Definitions, materials, spectra, absorption, grading, measurement and other files |
scaps_script_reference |
Search the installed SCAPS command list |
scaps_describe_device |
Layers, defects, interfaces with band offsets, contacts, realism checks |
scaps_edit_device |
Set commands, materials and solver numerics, saved as a new definition |
scaps_create_device |
New device from a layer, defect, interface and contact description |
scaps_import_file |
Add a shared SCAPS file and report missing referenced files |
scaps_write_data |
Write absorption, spectrum, generation, filter, grading or measurement files from data |
scaps_simulate |
One simulation with metrics, curves, profiles, analysis and checks |
scaps_batch |
Grid or paired sweeps over set and action keys |
scaps_optimize |
Fit measured curves or optimise a figure of merit |
scaps_jobs |
List, inspect, wait for or cancel runs |
scaps_results |
Paginated tables from any result file |
scaps_plot |
PNG plot of result curves and profiles |
scaps_run_script |
Validated SCAPS script for recorder, math, loops and tandem workflows |
scaps_sq_limit |
Detailed-balance limits for given band gaps and spectrum |
Definitions and run files are also available as scaps://definitions/{name} and scaps://runs/{run_id}/{file} resources.
Conventions
Keys and units follow the SCAPS script language: thickness in um, densities in cm^-3, interface densities in cm^-2, mobility in cm^2/Vs, velocity in cm/s, cross sections in cm^2, energies in eV, temperature in K. Layers, defects and interfaces count from 1, and layer 1 touches the left (back) contact. Contacts are addressed as contactleft and contactright.
Scripts cannot add the first bulk defect to a layer; scaps_create_device inserts one and configures it. Grading laws, per-level parameters of multivalent defects and the GUI curve fitter have no script commands; use grading files, scaps_optimize and definitions made in the GUI.
Safety
One SCAPS process runs per installation at a time, guarded by a file lock (fcntl on Linux, msvcrt on Windows) that all processes honour. Stopping the server, including with SIGTERM, stops the SCAPS process it started; a process left behind by a crash is stopped by the next run. File names must be bare names inside SCAPS folders. Scripts may not run system commands or open blocking dialogs. For isolation, remove the Wine drive mapping of the host root from the prefix.
Companion skill
The scaps-1d skill teaches an agent SCAPS workflows and realism rules. It works on its own and uses these tools when they are available.
Development
uv sync
uv run pytest
uv run pytest -m scaps
uv run ruff check src tests
Citation
Simulations made with SCAPS should cite M. Burgelman, P. Nollet and S. Degrave, Modelling polycrystalline semiconductor solar cells, Thin Solid Films 361-362 (2000) 527-532, doi:10.1016/S0040-6090(99)00825-1.
License
MIT
Metadata
Release files for scaps-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| scaps_mcp-0.1.0.tar.gz | 210.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scaps_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 268.7 kB
Release files / scaps_mcp-0.1.0.tar.gz
| Download URL | scaps_mcp-0.1.0.tar.gz |
|---|---|
| Size | 210.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec6d554fd613cccabbaef6925349f22db2f92bcca41ff0ca78c9dc862533ed72
|
|
BLAKE2b-256 checksum How to use checksums |
6497789619106527b854c3d387c941baafde235fe3b9a9d7ad3a010e46f41d9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / scaps_mcp-0.1.0-py3-none-any.whl
| Download URL | scaps_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 58.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
679f975913f0b4ee0cfad489528abdba93cc4c11591870cfee47ec19227df5cf
|
|
BLAKE2b-256 checksum How to use checksums |
ee6b76f8700474f6799033d79c13ba0f6f6903bc054c18e432cfb60c9fa21658
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for scaps-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.