This release is a pre-release and may not be stable for production use.
qualcoder-mcp is now Exegete
qualcoder-mcp is now called Exegete: a qualitative analysis
application you use in conversation with an AI assistant, compatible
with QualCoder. Its PyPI name, its command and its Python package are
exegete:
https://pypi.org/project/exegete/ and
https://github.com/nicotem/exegete.
This package is kept so that nothing you set up stops working. It
installs Exegete and keeps the qualcoder-mcp command and
python -m qualcoder_mcp.server, both of which start Exegete. It is
released beside every Exegete release until version 1.0.
What to change, if you want to, on each route:
- pip.
pip install --upgrade qualcoder-mcpkeeps bringing the current Exegete. To move to the new name:pip install exegete, change the command in your assistant's settings toexegete, and only thenpip uninstall qualcoder-mcp(which removes the old command). - pipx or uv.
pipx upgrade qualcoder-mcp,uv tool upgrade qualcoder-mcpanduvx qualcoder-mcpkeep working. These tools put only the named package's commands on your path, so you get theexegetecommand there only by installingexegeteitself (pipx install exegete,uv tool install exegete,uvx exegete). To move to the new name, in this order: installexegetefirst, then change the command in your assistant's settings to it, and only thenpipx uninstall qualcoder-mcporuv tool uninstall qualcoder-mcp(the other way round leaves no server). - Settings. Exegete's settings now start
EXEGETE_(for exampleEXEGETE_TOOLSET); the oldQUALCODER_MCP_...spellings andQUALCODER_PROJECT_PATHstill work until version 1.0.
Tidying up. exegete --check-transition (or
qualcoder-mcp --check-transition) lists what the change left on your
computer, numbered in the order to take the steps, with full paths
ready to paste, and changes nothing; with --tidy it removes the link
left at ~/.qualcoder_mcp once nothing it can find could still start
an older copy (an older package, a host's entry, or a desktop
extension older than Exegete). It cannot see a project's own
.mcp.json file: while an older copy could still start from one,
keep the link. Running this package's command writes one line saying
so.
Until version 1.0. At version 1.0 the last release of this package
will say plainly that it is the last, and none will follow; change your
settings to exegete before then.
The installation guide's section "Coming from qualcoder-mcp" says more: https://github.com/nicotem/exegete/blob/main/INSTALL.md
1 maintainer
Metadata
1 maintainer
Release files for qualcoder-mcp 0.14.2a0
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 | |
|---|---|---|---|---|
| qualcoder_mcp-0.14.2a0.tar.gz | 31.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qualcoder_mcp-0.14.2a0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.7 kB
Release files / qualcoder_mcp-0.14.2a0.tar.gz
| Download URL | qualcoder_mcp-0.14.2a0.tar.gz |
|---|---|
| Size | 31.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a64d6b5077a873c548c70a02f7275ba6645766e139449d38f9be94eca6a9718f
|
|
BLAKE2b-256 checksum How to use checksums |
4462daef3d856a9d7e738050a6a34b34d1bfc4aa8ef4a3937d38a7d8a9993eac
|
| 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 Oct 9, 2026.
Transparency logRelease files / qualcoder_mcp-0.14.2a0-py3-none-any.whl
| Download URL | qualcoder_mcp-0.14.2a0-py3-none-any.whl |
|---|---|
| Size | 31.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6185cb2dee7dcd69ceac02f26764b9aa042f9cd88c32a3b79627c4410e8a834
|
|
BLAKE2b-256 checksum How to use checksums |
0479171c960818f9b4e37e8fd80cdffbe4da6b997acdd49a767eded3cdf1c0ea
|
| 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 Oct 9, 2026.
Transparency logSecurity for qualcoder-mcp 0.14.2a0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for qualcoder_mcp-0.14.2a0.tar.gz
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 Oct 9, 2026.
Transparency logA 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.
