teasel
Connect lab instruments to AI assistants.
teasel is a CLI and TUI for configuring which instruments are available to your AI assistant. It browses the community instrument registry, prompts for connection details, and writes a .mcp.json file that Claude Code (or any MCP-compatible assistant) picks up automatically.
Quick start
uvx teasel
This opens the interactive TUI. Browse instruments, select one, enter your connection details, and the config is written.
CLI commands
# Add an instrument (prompts for required config)
uvx teasel add lecroy-wavesurfer
# Add with config inline
uvx teasel add lecroy-wavesurfer --set LECROY_HOST=192.168.1.111
# List configured instruments
uvx teasel list
# Remove an instrument
uvx teasel remove lecroy-wavesurfer
# Regenerate .mcp.json from saved state
uvx teasel apply
What it generates
teasel writes a .mcp.json in the current directory:
{
"mcpServers": {
"lab": {
"command": "uvx",
"args": ["teasel-server"],
"env": {
"LECROY_HOST": "192.168.1.111",
"PM5190_PORT": "/dev/ttyUSB0"
}
}
}
}
Claude Code reads this file and starts teasel-server automatically. You only need to run teasel once per project, or whenever your instrument setup changes.
Instrument state
Configured instruments are saved to ~/.config/teasel/instruments.toml. Running teasel apply in any directory regenerates .mcp.json from this state.
License
AGPL v3 — see LICENSE.
1 maintainer
Release files for teasel 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| teasel-0.3.2.tar.gz | 187.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| teasel-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 381.1 kB
Release files / teasel-0.3.2.tar.gz
| Download URL | teasel-0.3.2.tar.gz |
|---|---|
| Size | 187.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2589070205d44c33a4ddf78c568c108de4bb29a134af81bb2466cd050c4dc8bd
|
|
BLAKE2b-256 checksum How to use checksums |
1d3be100c7f0fd52449e1fc1aa2a08ec6de61a2e951baefd562536ec7d09a572
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / teasel-0.3.2-py3-none-any.whl
| Download URL | teasel-0.3.2-py3-none-any.whl |
|---|---|
| Size | 193.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87d47877780a80e4cd7b14fbdfba8cabcd9b1d3d06ec4915d038b0f6a5ef956c
|
|
BLAKE2b-256 checksum How to use checksums |
17d8d9a0527dd8b1a8f1aa68f16eb10028ff1f1a6e6004b60f242819ec99e56c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log
