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:
- On Claude web, open Customize → Connectors → Add custom connector.
- Use HTTP transport and paste
https://gemfit.ai/api/gemfit/mcp. - Complete GemFit OAuth once in the browser.
- 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.