Rename mcp.json gateway field to syncBackend

[elkimek]

Summary

Follow-up to a Greptile review on the app-repo mirror (get-based#227). Keeps the two .well-known/mcp.json copies in parity.

• Rename the gateway field to syncBackend. gateway next to "transport": "stdio" is ambiguous — a strict parser could read it as the MCP transport URL and try to connect to sync.getbased.health directly, instead of spawning getbased-mcp locally. syncBackend makes the role unambiguous: it's the data backend the local process talks to.
• Document the cross-repo mirror in CLAUDE.md so future version/tool/auth changes update both copies (Greptile flagged the silent-drift risk).

Test plan

• After deploy, curl https://getbased.health/.well-known/mcp.json shows syncBackend and validates as JSON
• Matches the corresponding change in get-based#227

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
get-based-site	Ready	Preview, Comment	May 14, 2026 11:23am

[greptile-apps]

Greptile Summary

Renames the non-standard gateway field in .well-known/mcp.json to syncBackend to eliminate ambiguity with MCP transport URLs, and adds a CLAUDE.md note documenting the cross-repo mirror relationship with the app repo.

• The field rename in mcp.json is a one-line cosmetic change with no functional impact — syncBackend is a custom field not part of the MCP spec, so no parser will break on it.
• The CLAUDE.md addition captures the sync requirement (version, tool list, auth, sha256 digest) that was previously undocumented, reducing future silent-drift risk.

Confidence Score: 5/5

Safe to merge — the change is a one-line rename of a custom non-standard field and a documentation addition with no runtime impact.

Both changes are non-functional: the renamed field is a custom extension not parsed by any MCP transport layer, and the CLAUDE.md update is purely documentation. No logic, auth, or data-path is touched.

No files require special attention.

Important Files Changed

Filename	Overview
.well-known/mcp.json	Renames the custom gateway field to syncBackend — a non-breaking, clarifying rename of a non-standard field with no other changes.
CLAUDE.md	Adds one bullet to the structure section documenting that .well-known/ files are mirrored into the app repo and outlining sync requirements.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["MCP client discovers\n/.well-known/mcp.json"] --> B["Reads transport: stdio\nhosting: local"]
    B --> C["Spawns getbased-mcp\nprocess locally"]
    C --> D["getbased-mcp reads\nsyncBackend URL"]
    D --> E["Fetches context data from\nhttps://sync.getbased.health"]
    E --> F["Returns health data\nto MCP client"]
    style D fill:#d4edda,stroke:#28a745

Loading

_{Reviews (1): Last reviewed commit: "Rename mcp.json gateway field to syncBac..." | Re-trigger Greptile}