interloper-mcp
A Model Context Protocol server exposing the interloper platform to AI agents: catalog definitions, the collection, lineage, run/backfill monitoring, analytics and, for tokens holding the editor role, the writes (edits, creates, triggers, retries, cancels).
Authentication uses personal access tokens (PATs) minted via the
interloper API (POST /api/tokens, session-authenticated). Tokens are
org-scoped and carry the holder's live role; revocation and membership
removal apply immediately.
Running
Streamable HTTP (default; binds INTERLOPER_MCP_HOST:INTERLOPER_MCP_PORT,
endpoint /mcp):
interloper-mcp
Clients authenticate every request with Authorization: Bearer ilp_....
stdio (single-user, authenticates once at startup):
INTERLOPER_MCP_TOKEN=ilp_... interloper-mcp --transport stdio
For local development without a token, INTERLOPER_MCP_ORG_ID=<uuid> scopes
the stdio server to one organisation directly.
Connecting clients
MCP Inspector:
npx @modelcontextprotocol/inspector
# Transport: Streamable HTTP, URL: http://localhost:3001/mcp
# Header: Authorization: Bearer ilp_...
Claude Code:
claude mcp add --transport http interloper http://localhost:3001/mcp \
--header "Authorization: Bearer ilp_..."
Settings
| Env var | Default | Purpose |
|---|---|---|
INTERLOPER_MCP_HOST |
0.0.0.0 |
HTTP bind host |
INTERLOPER_MCP_PORT |
3001 |
HTTP bind port |
INTERLOPER_MCP_EXTERNAL_URL |
— | Public base URL (e.g. https://mcp.interloper.app), used in OAuth protected-resource metadata |
INTERLOPER_MCP_TOKEN |
— | stdio only: PAT to authenticate as |
INTERLOPER_MCP_ORG_ID |
— | stdio only: dev fallback, direct org scope |
Database and catalog configuration is the standard interloper set
(INTERLOPER_POSTGRES_*, INTERLOPER_CATALOG, ...).
Deployment
The mcp dockerfile target ships as interloper-mcp:<version> alongside the
other role images (Makefile ROLES + the publish workflow). The Helm chart
deploys it with mcp.enabled=true — the workload shares the release's
Postgres/catalog configuration, sets INTERLOPER_MCP_EXTERNAL_URL from
mcp.externalUrl, and the chart's HTTPRoute forwards /mcp and
/.well-known/oauth-protected-resource on the app hostnames to it. What
remains for the operator is supplying the environment values and, if it should
not share the app's identity, a database identity of its own.
Metadata
Release files for interloper-mcp 0.118.0
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 |
|---|---|---|---|---|
| interloper_mcp-0.118.0.tar.gz | 7.4 kB | Without provenance | Details for interloper_mcp-0.118.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| interloper_mcp-0.118.0-py3-none-any.whl | Python 3 | none | any | Details for interloper_mcp-0.118.0-py3-none-any.whl |
Total release size: 16.6 kB
Release files / interloper_mcp-0.118.0.tar.gz
| Download URL | interloper_mcp-0.118.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6735e046ebfa310a61dfe6f7adf8baccd6bcec7d0743ce872332ede62f673dad
|
|
BLAKE2b-256 checksum How to use checksums |
1d17e090b46cbd521fb9a96a2dcad30902b0c4842f7db74eed5931922b27bd78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / interloper_mcp-0.118.0-py3-none-any.whl
| Download URL | interloper_mcp-0.118.0-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f23a25468c1122b5550e40e4068fb516403caf279b69d30cc017609ad51a9892
|
|
BLAKE2b-256 checksum How to use checksums |
f372f79bfb9e2d7463a78826b84bed0ea277b8a009a338af9d1a7bccfccc6672
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for interloper-mcp 0.118.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.
