gcontext connector — local MCP bridge: cloud structure, local secret values
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"gcontext-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# gcontext **The workspace your agent works in**: tasks it tracks, integrations it operates, scripts it runs. Structure lives in the cloud so every session starts oriented; **secret values and script execution never leave your machine**. One prompt like *"ship the launch discount: new payment link in Stripe, point promo.example.com at the site, update the launch task"* and your agent reads the integration docs, runs the scripts locally with keys injected from your local secret store, and checks off the task, without a single key entering the conversation. ## Get started (2 minutes) ```bash uvx gcontext-mcp login # browser sign-in at https://app.gcontext.ai mints a token ``` Then add it to Claude Code: ```bash claude mcp add-json gcontext '{ "type": "stdio", "command": "uvx", "args": ["gcontext-mcp"], "env": { "GCONTEXT_TOKEN": "<your token>" } }' ``` Free up to 30 files, no credit card. Needs `uv`/`uvx` on your PATH. ## What your agent gets - **Tasks**: typed folders with goals, steps, and progress notes the agent maintains, so the next session picks up exactly where the last one stopped. - **Integrations**: docs per third-party service (what it is, allowed/never operations, which secret NAMES it needs) that act as the agent's operations manual and guardrails. - **Local script execution**: `tool_run_script` runs Python on YOUR machine with secret values injected from `~/.gcontext/.env` (chmod 0600; OS keychain opt-in via `GCONTEXT_SECRET_BACKEND=keychain`) and scrubbed from every output the agent sees. - **A secret-name registry**: the cloud knows only NAMES and descriptions; values are filled once via a local browser form and stay on your machine. ## The privacy split | Lives in the cloud | Never leaves your machine | |---|---| | Folder structure, docs, task state | Secret VALUES (`~/.gcontext/.env`, keychain opt-in) | | Secret NAMES + present/missing flags | Script and shell execution | | Activity metadata (names, token counts) | …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.