jobescape-concierge 0.1.2

Concierge MCP server — connects Claude (and other MCP clients) to the Concierge BigQuery assistant over stdio.

jobescape-concierge

Concierge MCP server. Connects Claude (and any MCP-compatible client) to the Concierge BigQuery assistant over stdio — no repo clone, no database or cloud credentials required.

Requirements

• uv installed (for uvx)
• A Concierge API token (request one from the Concierge admin; tokens are tied to your @nvs.team email)

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