Skip to content

fix(mcp): route to cloud /v1 HTTP client in self_hosted mode (0.2.2)#7

Merged
andrei-hasna merged 1 commit into
mainfrom
feat/mcp-cloud-http-client
Jul 7, 2026
Merged

fix(mcp): route to cloud /v1 HTTP client in self_hosted mode (0.2.2)#7
andrei-hasna merged 1 commit into
mainfrom
feat/mcp-cloud-http-client

Conversation

@andrei-hasna

Copy link
Copy Markdown
Contributor

MCP client path ignored self_hosted API env vars (only local + in-VPC Postgres DSN). Now prefers the locked API-client path: when HASNA_IDENTITIES_API_URL+HASNA_IDENTITIES_API_KEY are set, routes ALL reads/writes through CloudHttpIdentityStore -> identities.hasna.xyz/v1 with bearer key (no DSN on clients). Matches CLI/SDK resolver from #6. verify:release green (64 tests). Live CLI create/verify/delete proven against cloud; unset -> local. Bump 0.2.1 -> 0.2.2.

The identities MCP server previously only knew the local file store and the
in-VPC Postgres DSN path (HASNA_IDENTITIES_STORAGE_MODE=cloud). On a client
machine with the self_hosted env vars set it silently ignored them and read
local. Prefer the locked API-client path: when HASNA_IDENTITIES_API_URL and
HASNA_IDENTITIES_API_KEY are set, route ALL reads/writes to <app>/v1 with the
bearer key (no DSN on clients). Unsetting restores the local store.

Bump 0.2.1 -> 0.2.2.
@andrei-hasna
andrei-hasna merged commit 1ccaae9 into main Jul 7, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant