Stays where you work
Ask the chat in the same window as your code. No Alt-Tab, no second app, no context switch.
Cursor is the AI-native editor most working developers use day to day. Drop in the Getwello MCP server and you can ask the editor about your Circle without leaving the file you're in. Same install as the Claude Desktop setup.
Coordinator-only. Included in the £4.99 plan. Same day to set up.
async function digest() {
const stats = await getwello
.get_circle_stats({
circle_id: process.env.CIRCLE,
});
const mood = await getwello
.list_mood_history({
circle_id: process.env.CIRCLE,
days: 7,
});
return render(stats, mood);
}Ask the chat in the same window as your code. No Alt-Tab, no second app, no context switch.
Have the AI draft a digest, an SQL query against an exported Sheet, anything. Pulls live Getwello data, writes the code, hands it back.
Coordinator role, active subscription, revocable key. The MCP server enforces them identically.
Cursor's subscription pays for the AI inference; Getwello is free. Same economic model as Claude Desktop.
# ~/.cursor/mcp.json
{
"mcpServers": {
"getwello": {
"command": "npx",
"args": ["-y", "@getwello-app/mcp-server"],
"env": { "GETWELLO_API_KEY": "gw_live_..." }
}
}
}If you've already wired the MCP server into Claude Desktop, this is a five-second copy-paste. The exact same npx invocation, the exact same env var, the exact same tools list.
Open Settings → Developer API as a Coordinator. Name the key 'Cursor on my MacBook'. Copy the gw_live_ token.
Either edit ~/.cursor/mcp.json directly, or use Cursor's in-app MCP Settings to add a new server.
Use the same npx config as Claude Desktop. Save the file.
Quit Cursor properly, reopen, open Composer or Chat. Ask 'list my Getwello Circles'. If the list comes back, you're live.
Almost. The MCP server package is identical; only the config file path differs. Cursor reads from ~/.cursor/mcp.json (or the in-app MCP settings). Drop the same snippet in and it works.
If you're a Coordinator who lives in Cursor for work, asking the editor 'has Mum checked in?' while you're already there is friction-free. Plus you can build small tools inline (digests, scripts, automations) without leaving the editor.
Yes. Each app maintains its own MCP config. Same API key works for both; you can also mint separate keys per editor for cleaner audit trails.
Whatever you ask Cursor's AI travels through whichever model provider you've configured. If that's a privacy concern, switch Cursor to a local Ollama model and the data stays on your machine.
Yes. Composer can call the same MCP tools as the chat. Useful for one-shot generation tasks like 'draft this week's digest using the last seven check-ins.'
Some families wire two or three at the same time. The webhook fans out, the API keys stay the same.
See every integration or jump to the Developer API overview.
Mint your first API key in two minutes. Coordinator-only. Included in the £4.99 family plan.