Qualty MCP User Setup
This guide shows how to install and use the published qualty-mcp package from PyPI in a new project, for both Claude Code and Cursor.
Prerequisites
- Python 3.11+ available on your machine
pipxinstalled- A Qualty API token (
qlty_ci_...)
Install pipx if needed:
python3 -m pip install --user --upgrade pipx
python3 -m pipx ensurepath
Open a new terminal after ensurepath.
1) Install Qualty MCP
pipx install qualty-mcp
If already installed and you want latest:
pipx upgrade qualty-mcp
2) Go to your project folder
cd /path/to/your-project
All project-specific files (.mcp.json, .qualty.json) will be created in the current folder.
3) Initialize token + default project
qualty-mcp init
This will:
- prompt for your
qlty_ci_...token - fetch projects in your account
- let you pick an active project for this workspace
Notes:
- token is stored globally at
~/.qualty/credentials - active project is stored per project in
.qualty.json
4A) Configure MCP for Claude Code
qualty-mcp install-claude-code
4B) Configure MCP for Cursor
qualty-mcp install-cursor
5) Restart your client
After writing .mcp.json, fully restart:
- Claude Code, or
- Cursor
This reloads MCP servers and starts qualty-mcp serve.
6) Verify setup
From the same project directory:
qualty-mcp doctor
qualty-mcp status
Expected:
- token configured
- API reachable
- default project configured
Common commands
List/switch active project for this workspace
qualty-mcp list-projects
or directly:
qualty-mcp switch-project --project-id 123
qualty-mcp switch-project --project-name "My Project"
Show config snippet only
qualty-mcp print-claude-code-config
qualty-mcp print-cursor-config
File model (important)
-
~/.qualty/credentials
Global token for this OS user (shared across folders) -
.qualty.json
Per-project active project defaults -
.mcp.json
Per-project MCP launch config for Claude Code/Cursor
Troubleshooting
Could not fetch projects: [Errno 8] nodename nor servname provided
This usually means local/network DNS issues or restricted network environment.
First verify package defaults:
qualty-mcp doctor
qualty-mcp status
Then restart client.
MCP changes not reflected
- Confirm you are in the right project folder
- Re-run install command for that project
- Restart Claude Code/Cursor
Reconfigure token
rm -f ~/.qualty/credentials
qualty-mcp init
Quickstart (copy/paste)
pipx install qualty-mcp
cd /path/to/your-project
qualty-mcp init
qualty-mcp install-claude-code
qualty-mcp doctor
Use install-cursor instead of install-claude-code if needed.
Metadata
Release files for qualty-mcp 0.1.3
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 | Actions |
|---|---|---|---|---|
| qualty_mcp-0.1.3.tar.gz | 59.7 MB | With provenance | Details for qualty_mcp-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qualty_mcp-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for qualty_mcp-0.1.3-py3-none-any.whl |
Total release size: 59.8 MB
Release files / qualty_mcp-0.1.3.tar.gz
| Download URL | qualty_mcp-0.1.3.tar.gz |
|---|---|
| Size | 59.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f286760ca83dd94105024311920e06725e3bc55beb3fad172b3f7f177253308
|
|
BLAKE2b-256 checksum How to use checksums |
eb0bb4e848a8d241456862b0927b45bf10ac7800470449cdd790868063d69e7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency logRelease files / qualty_mcp-0.1.3-py3-none-any.whl
| Download URL | qualty_mcp-0.1.3-py3-none-any.whl |
|---|---|
| Size | 51.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
18aea38b3b2940574b5e8f98604b1f4411b22fb2a4ceb85a135d595f40de240e
|
|
BLAKE2b-256 checksum How to use checksums |
61e04fea829df5a9ca4d3b669832a06e9397192187351a5aac6ea090b3e59bcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency logSecurity for qualty-mcp 0.1.3
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 qualty_mcp-0.1.3.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 May 18, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.