This release is a pre-release and may not be stable for production use.
stubborn-mcp
MCP server for Stubborn — exposes source-neutral code and contract graph tools to Cursor and other MCP clients.
Thin adapter over stubborn.api. All compile and contract graph logic lives in stubborn-stub.
Part of the stubborn-ai program — see stubborn-hub.
Install
pip install stubborn-stub stubborn-mcp
stubborn try # bundled fixture smoke test (no Java)
For binary/NDJSON SCIP indexing, install Stubborn with its SCIP extra:
pip install "stubborn-stub[scip]" stubborn-mcp
stubborn index --scip index.scip --out metadata/symbols.db
export STUBBORN_DB=metadata/symbols.db
stubborn-mcp
Contract-only databases are also supported:
stubborn index-openapi \
--openapi openapi.json \
--service customers-service \
--workspace petclinic \
--out metadata/symbols.db
export STUBBORN_DB=metadata/symbols.db
stubborn-mcp
Cursor configuration
.cursor/mcp.json:
{
"mcpServers": {
"stubborn": {
"command": "stubborn-mcp",
"env": {
"STUBBORN_DB": "${workspaceFolder}/metadata/symbols.db"
}
}
}
}
Module entry: python -m stubborn_mcp
Tools
| Tool | Purpose |
|---|---|
workspace_info |
Inspect workspace source kinds: code repos, contract sources, symbols, endpoints |
get_context |
Prune + weave code or contract context (java-stub or stubborn-dsl) |
list_symbols |
Browse/search symbols by stable_id |
list_contracts |
Browse/search OpenAPI contract endpoint stable IDs and schema constraints |
metrics |
Compression KPI vs source tree |
Full parameter reference: docs/MCP.md
Setup diagnostics
Read-only MCP and DB checks (ADR-015) — does not start the MCP server:
export STUBBORN_DB=metadata/symbols.db
stubborn-mcp doctor
stubborn-mcp doctor --json
Aggregate with sibling packages: stubborn-hub DEMO-LAUNCHERS.
Development
git clone https://github.com/stubborn-ai/stubborn-mcp.git
cd stubborn-mcp
pip install -e "../stubborn"
pip install -e ".[dev]"
pytest
License
MIT — see LICENSE.
Metadata
Release files for stubborn-mcp 0.10.0b2
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 |
|---|---|---|---|---|
| stubborn_mcp-0.10.0b2.tar.gz | 11.2 kB | Without provenance | Details for stubborn_mcp-0.10.0b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stubborn_mcp-0.10.0b2-py3-none-any.whl | Python 3 | none | any | Details for stubborn_mcp-0.10.0b2-py3-none-any.whl |
Total release size: 21.8 kB
Release files / stubborn_mcp-0.10.0b2.tar.gz
| Download URL | stubborn_mcp-0.10.0b2.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60107507df2cda4125904d68cb9b35b9ae65860ca441f381cdbbf8642cfd9f87
|
|
BLAKE2b-256 checksum How to use checksums |
c5c3beb57e46da31750ae79be587a142b62e6250d7af6cb096221303a965067e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / stubborn_mcp-0.10.0b2-py3-none-any.whl
| Download URL | stubborn_mcp-0.10.0b2-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d7f3ac1d3d56ba7f822a83af19a398a4ddfd61ac76b69e17bbc3882ab417d3f8
|
|
BLAKE2b-256 checksum How to use checksums |
8a46e748ffd0c827c9e990532c39326cf83c9491f635d7f1af908348b04803bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for stubborn-mcp 0.10.0b2
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.