Skip to main content

selph-mcp

Status: shelved (2026-04-24). The remote MCP surface mounted on ingestion_api is the supported way to reach Selph. This stdio wheel is not actively maintained: HttpEngineAdapter still works against the cloud, but InProcessEngineAdapter remains a stub, so installing the wheel buys clients nothing they can't get from remote MCP. Code stays in tree as optionality. Revisit if (a) a client requires stdio specifically, or (b) Selph commits to a self-hosted product where InProcessEngineAdapter runs the kernel locally against a client-owned Neo4j + Postgres + Azure OpenAI.

Selph MCP stdio transport. Install with pipx:

pipx install selph-mcp

Then register with your Selph engine:

selph-mcp-bootstrap register \
    --engine-url https://<your-engine>.azurecontainerapps.io \
    --admin-key <SELPH_API_KEY> \
    --user-id U001 \
    --display-name "MyClaudeCode"

Paste the printed JSON snippet into ~/.claude.json and reload Claude Code.

Diagnostics: selph-mcp-bootstrap doctor # check contract-version compatibility selph-mcp-bootstrap whoami # print consumer info

Metadata

Release files for selph-mcp 1.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for selph-mcp 1.5.0
File Interpreter ABI Platform Actions
selph_mcp-1.5.0-py3-none-any.whl Python 3 none any Details for selph_mcp-1.5.0-py3-none-any.whl

Release files / selph_mcp-1.5.0-py3-none-any.whl

Download URL selph_mcp-1.5.0-py3-none-any.whl
Size 445.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2baa3466a595d5a3f841bf0a2f844c08eb9a66ba8fedc3050b91953abb5d303a
BLAKE2b-256 checksum
How to use checksums
14e5e615b4fa1054920d41fb94605a3a6bb6e1cee58101a902b12e1edc27310e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.12

Security for selph-mcp 1.5.0

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page