Two ways to chat inside Kenki (Options 1 and 3: pick one, switch anytime from the chat). Option 2 connects an outside AI agent (Claude, Cursor, Cline, or any MCP client). Option 4 is a one-off copy-paste.
Option 1 · Use Kenki AI
Kenki's built-in AI.
No API key, no setup. Included with any paid plan. Chat from the dashboard. Kenki logs water, food, vitals, sleep on your behalf.
Checking your plan…
Kenki AI is included with any paid plan. No key, no setup.
Active
- / - messages used this month
Resets the first of each UTC month. To add your own provider, save a key in Option 3.
Active
- / - messages used this month
When you chat from the dashboard, run with:
Resets monthly. Switching is instant. The next message uses the selected provider.
Option 2 · Your AI agent
Plug an outside agent into Kenki.
A separate surface from the in-app chat. Connect an MCP client you already use (Claude, Cursor, Cline, Zed, and others) and chat there. It reads your data and logs entries through Kenki's tools.
Heads up. Full access lets your agent modify anything in your Kenki account. Only enable this for an agent you control. Revoke anytime below.
Custom scopes (advanced)
Grant exactly what this token can do, overrides the choice above when any box is checked. Read scopes are free; any write scope needs a paid plan.
Read
Write · paid
Token created. Give this prompt to your AI agent.
Best for tool-using agents like Claude, Cursor, and Cline. The agent should install the MCP config, reload tools, list Kenki tools, then tell you it worked.
Agent setup prompt
Paste the prompt into the AI agent you want to connect. It includes the config and tells the agent to verify the tools.
If your client has a manual MCP settings screen, expand Raw MCP config below and paste the JSON.
Note: this is HTTP JSON-RPC, not SSE. If your client offers both, pick "HTTP". Agent-readable setup guide: /.well-known/kenki-mcp.md.
▸ Raw MCP config · for manual client settings
We don't keep a copy of the token. Save it somewhere safe. If you lose it, connect again and revoke the old one.
▸ Manual fields · if your client asks for URL + token separately
URL
https://kenki.ai/mcp
Authorization header
Token only (no "Bearer " prefix)
▸ Older clients · local stdio bridge fallback
If your client doesn't support remote MCP yet, run a local Node bridge:
Option 3 · API key
Bring your own API key.
Use Kenki's chat with your OpenAI, Google, or Anthropic key. Your bill, your model. Encrypted, never leaves the server. The chat can log water, food, vitals, sleep, and supplements when you ask. For an external agent, use Option 2.
Not connected
Get a key from your provider's dashboard. We encrypt it before storing.
Option 4 · Quick paste
Copy Markdown health snapshot.
Plain Markdown summary of the last 7 days. No setup, no token. Copy, then paste into Claude.ai, ChatGPT, Gemini, or Perplexity.
- 1 Click Copy snapshot.
- 2 Open your AI of choice and paste. Add your question.
- 3 The snapshot stays on your clipboard. Kenki never sees it leave.
Profile, goals, and 7 days of water, sleep, recovery, food, vitals, meds, supplements, and body. Want everything? Settings → Data has the full archive.
Connected agents
Active connections.
Revoke any of these to immediately cut off access.
No active connections.
Agent activity
What your agents did.
A read-only log of every call your connected agents made, the action, the endpoint, and when. No message content, health data, or keys are recorded.
Loading…