jobescape-concierge
Concierge MCP server. Connects Claude (and any MCP-compatible client) to the Concierge ClickHouse assistant over stdio — no repo clone, no database or cloud credentials required.
Requirements
uvinstalled (foruvx)- A Concierge API token (request one from the Concierge admin; tokens are tied to your
@nvs.teamemail)
Add to Claude Desktop / Claude Code
claude mcp add concierge \
-e CONCIERGE_API_TOKEN=t2s_... \
-- uvx jobescape-concierge
Or edit claude_desktop_config.json directly:
{
"mcpServers": {
"concierge": {
"command": "uvx",
"args": ["jobescape-concierge"],
"env": {
"CONCIERGE_API_TOKEN": "t2s_..."
}
}
}
}
Replace t2s_... with your actual token, then fully quit and reopen Claude Desktop.
Local development
Point the server at a locally running Concierge instance:
CONCIERGE_API_TOKEN=t2s_... CONCIERGE_MCP_URL=http://localhost:8080/mcp/ uvx jobescape-concierge
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
CONCIERGE_API_TOKEN |
Yes | — | Plaintext API token (t2s_... prefix). |
CONCIERGE_MCP_URL |
No | https://concierge-yh7apzuicq-ue.a.run.app/mcp/ |
Base URL for the Concierge MCP endpoint. Use a localhost URL for local dev. |
How it works
On startup the server connects to the Concierge cloud MCP endpoint over HTTPS, validates your token, and fetches the available tool list. It then re-serves those tools over the MCP stdio protocol and forwards every tool call to the cloud. No SQL, schema, or credentials live in this package — all data access happens server-side.
License
MIT
Metadata
Release files for jobescape-concierge 0.1.5
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 | |
|---|---|---|---|---|
| jobescape_concierge-0.1.5.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jobescape_concierge-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.8 kB
Release files / jobescape_concierge-0.1.5.tar.gz
| Download URL | jobescape_concierge-0.1.5.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffdd391cf196e04c8b6406d302345e8f9c4fcfdf0ecff74728296a33c4150dea
|
|
BLAKE2b-256 checksum How to use checksums |
0959bf12c7d3697fb209d628403fdcfbcf3b40c67c310e3611591a85bb15ca75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","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 / jobescape_concierge-0.1.5-py3-none-any.whl
| Download URL | jobescape_concierge-0.1.5-py3-none-any.whl |
|---|---|
| Size | 4.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
311a0755d58971ff3ee9acffabb86ccc564fc284a1ee56f3f2d0fc03a6daea37
|
|
BLAKE2b-256 checksum How to use checksums |
5ca94fac4343e798e1188296eba441ee845aa8303b54397ad341635ef894994b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","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 jobescape-concierge 0.1.5
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.