Model Context Protocol

Connect GemFit to your AI assistant.

GemFit provides a secure MCP server for Claude Code, OpenAI/Codex, OpenClaw, LM Studio, MCP Inspector, and other compatible clients. Approved assistants can read your fitness context and prepare editable review drafts for meals, workouts, body metrics, plans, edits, and deletes.

Connection Details

Remote MCP endpoint:

https://gemfit.ai/api/gemfit/mcp

OAuth discovery:

https://gemfit.ai/.well-known/oauth-protected-resource/api/gemfit/mcp
https://gemfit.ai/.well-known/oauth-protected-resource
https://gemfit.ai/.well-known/oauth-authorization-server

Claude Code setup:

claude mcp add --transport http gemfit https://gemfit.ai/api/gemfit/mcp

Claude app + mobile setup:

  1. On Claude web, open Customize → Connectors → Add custom connector.
  2. Use HTTP transport and paste https://gemfit.ai/api/gemfit/mcp.
  3. Complete GemFit OAuth once in the browser.
  4. Open Claude mobile and enable GemFit from the chat connector/tools menu.

Claude mobile can use the account-level connector after web setup. Add new custom connectors from Claude web.

OpenClaw, Codex, and generic HTTP MCP clients:

{
  "name": "GemFit MCP",
  "transport": "http",
  "url": "https://gemfit.ai/api/gemfit/mcp"
}

LM Studio mcp.json:

{
  "mcpServers": {
    "gemfit": {
      "url": "https://gemfit.ai/api/gemfit/mcp"
    }
  }
}

A 401 response from the MCP endpoint is expected before OAuth. It means the assistant needs user approval, not that the server is missing.

Plain text for AI clients

Fetch https://gemfit.ai/mcp.txt for a compact machine-readable setup note.

Security Model

  • No MCP tool accepts caller-controlled user_id.
  • No business/admin tools are exposed.
  • No personal API key is required for standard clients; OAuth creates scoped, revocable access.
  • External writes create pending review cards first.
  • Durable saves require GemFit review or explicit chat approval with logs.confirm.
  • Users can revoke connected apps in GemFit Connect.
profile.read goals.read nutrition.read workouts.read body.read trends.read logs.draft logs.confirm

Available Tools

  • gemfit_get_profile_context
  • gemfit_get_day_summary
  • gemfit_search_logs
  • gemfit_get_goals
  • gemfit_get_recent_trends
  • gemfit_get_data_quality_report
  • gemfit_create_food_log_draft
  • gemfit_create_workout_log_draft
  • gemfit_build_workout_plan_draft
  • gemfit_create_body_metric_draft
  • gemfit_create_trackable_log_draft
  • gemfit_create_fitness_journal_draft
  • gemfit_create_goal_update_draft
  • gemfit_update_log_draft
  • gemfit_delete_log_draft
  • gemfit_list_pending_actions
  • gemfit_confirm_pending_action
  • gemfit_reject_pending_actions

Client Guidance

First call gemfit_get_profile_context, then read the relevant day summary. For food or workout logging, create draft cards and return review links. Use profile context for workout calorie burn when it is available.

Public pages are documentation only. The MCP server enforces OAuth, scopes, user ownership, review drafts, and audit logs.