confluence-knowledge (local MCP service)
Local companion service for the confluence-knowledge Copilot agent.
See ../../docs/confluence-knowledge.md for the full guide.
- GET-only
ConfluenceClient— non-GET raisesSecurityExceptionpre-flight. - Recursive subtree crawl (Cloud v2 + Data Center), resumable.
- Local ONNX embeddings (
nomic-embed-text-v1.5, quantized) + sparse leg (Qdrant/bm25)- reranker (
mxbai-rerank-xsmall-v1, quantized) — MIT/Apache-2.0, pinned inmodels.lock.json, no torch, never a cloud embedding call.
- reranker (
- SQLite + FTS5 + vector-blob index under
.conf_knowledge_index/. - Credentials via OS keyring / env var / chmod-600
.conf_auth.json.
Dev
python3.11+ -m venv .venv && .venv/bin/pip install -e '.[dev]'
.venv/bin/python -m pytest # all offline — no network needed
.venv/bin/python -m ruff check src tests
Before every release, run the end-to-end smoke test. It spawns the real stdio server through the MCP client SDK and uses the real models against a fake Confluence on localhost, with simulated network latency:
.venv/bin/pip install -e '.[models]'
CONF_KNOWLEDGE_HOME=/tmp/ck/home .venv/bin/confluence-knowledge prepare-models
CONF_KNOWLEDGE_HOME=/tmp/ck/home .venv/bin/python scripts/e2e_smoke.py # ends with "E2E OK"
e2e_bootstrap.py goes further — it replays the agent's entire install flow
in a sandboxed $HOME (python discovery → venv → pip install from the
shipped dist/ bundle → models → credentials → register → the real server
over stdio → a full Q&A round-trip). Run it before every release:
CK_MODEL_CACHE=/tmp/ck/home/models .venv/bin/python scripts/e2e_bootstrap.py # "E2E BOOTSTRAP OK"
CLI
| Command | Purpose |
|---|---|
confluence-knowledge setup |
guided env/site/token setup (hidden input, keyring) |
confluence-knowledge prepare-models |
fetch pinned local models once |
confluence-knowledge doctor |
verify config + heartbeat + models |
confluence-knowledge serve |
run the stdio MCP server (what the IDE launches) |
confluence-knowledge clean |
delete the local index (~/.confluence-knowledge/work unless CONF_KNOWLEDGE_WORKDIR is set) |
1 maintainer
Metadata
1 maintainer
Release files for confluence-knowledge 0.11.1
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 | |
|---|---|---|---|---|
| confluence_knowledge-0.11.1.tar.gz | 172.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| confluence_knowledge-0.11.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 292.8 kB
Release files / confluence_knowledge-0.11.1.tar.gz
| Download URL | confluence_knowledge-0.11.1.tar.gz |
|---|---|
| Size | 172.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e4015d795654ef0dc2b99ebb832e79090b6822977cf0c4ccec96537b4905125
|
|
BLAKE2b-256 checksum How to use checksums |
daa93fae5486d30980337a3da4a419438ce97180f9446259a3aaad4c156a2ff9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / confluence_knowledge-0.11.1-py3-none-any.whl
| Download URL | confluence_knowledge-0.11.1-py3-none-any.whl |
|---|---|
| Size | 120.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60631ae710fc8fd0954ae4c89619abbbc6deadaba1358cecef57379d50533857
|
|
BLAKE2b-256 checksum How to use checksums |
ef7ef7794ee692cbac33609cca2565f5b96c5fabec656d578965f0dd50a2a737
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for confluence-knowledge 0.11.1
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.
