Connect an assistant (MCP)

Claude.ai (custom connector, OAuth)

1. Open Claude's connector settings (Settings, then Connectors) and choose to add a custom connector. On Team and Enterprise plans an organization owner adds it first. Custom connectors are not on every plan: check Anthropic's docs.
2. Name it Call Me Awake and enter the URL https://staging.callmeawake.com/mcp. Leave any OAuth client ID and secret fields empty: the client registers itself.
3. Choose Connect. You are sent to Call Me Awake to sign in, then to a screen that says the assistant wants to manage your wake-up calls. Approve it.
4. Back in a chat, turn the connector on from the tools menu, then ask for a call.

You can disconnect any assistant later under connected apps in your settings.

Claude Desktop

Add it as a custom connector, exactly as for Claude.ai above, with the same URL (https://staging.callmeawake.com/mcp) and the same sign-in. This is the supported way to add a remote server; check Anthropic's docs for where Claude Desktop shows connectors.

The claude_desktop_config.json file is for local servers that Claude Desktop starts itself and does not take a remote URL. If you want a key-based setup there, a bridge such as the third-party mcp-remote package can proxy a remote server. We have not tested it: check its docs before relying on it.

{
  "mcpServers": {
    "call-me-awake": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://staging.callmeawake.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer wk_..." }
    }
  }
}

Claude Code

With OAuth (you sign in once in the browser):

claude mcp add --transport http call-me-awake https://staging.callmeawake.com/mcp

Then start claude, run /mcp, pick call-me-awake and choose to authenticate.

With an API key instead (no browser step; good for scripts and headless machines):

claude mcp add --transport http call-me-awake https://staging.callmeawake.com/mcp \
  --header "Authorization: Bearer wk_..."

claude mcp list shows whether it connected. By default the server is saved for you in this project only; the options for sharing it are in Claude Code's docs. Never commit a key to a shared project file.

Cursor (API key)

Use an API key, not OAuth. Cursor's sign-in returns through a cursor:// link, and Call Me Awake only accepts https and loopback redirects for OAuth clients, so the OAuth flow cannot complete. If a later Cursor release offers an https redirect, OAuth will work: check Cursor's docs.

Add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project; do not commit a key). Check Cursor's docs for the current file format.

{
  "mcpServers": {
    "call-me-awake": {
      "url": "https://staging.callmeawake.com/mcp",
      "headers": { "Authorization": "Bearer wk_..." }
    }
  }
}

ChatGPT

ChatGPT can connect to a remote MCP server as a custom connector on some plans (it may sit behind a developer-mode switch). Give it the URL https://staging.callmeawake.com/mcp and choose OAuth. We have not been able to confirm the current menus or plan requirements: check OpenAI's docs.

Any other MCP client

Point it at https://staging.callmeawake.com/mcp as a remote (Streamable HTTP) server. A client that supports MCP's OAuth flow finds everything it needs from the 401 challenge. One that does not takes a header: Authorization: Bearer wk_.... To check a key by hand:

curl -sS https://staging.callmeawake.com/mcp \
  -H "Authorization: Bearer wk_..." \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

API keys

An API key is a long secret that starts with wk_. Send it as Authorization: Bearer wk_.... The same key works for the REST API. Create one from your account (see POST /api/v1/api-keys in the API reference). The full key is shown once, so store it like a password; delete it to revoke it.

A key has the read and write scopes unless you choose fewer. Downloading the full account export over the REST API needs the export scope, which a key has only if you add it when you make the key. Making or deleting keys, registering or removing a phone or browser, and deleting the account are never possible with a key: use the app or the web.

A key gives whoever holds it the same access as an assistant you signed in: keep it out of chats, screenshots and shared config files.

get_time_context read-only

ALWAYS call this first before creating, moving, or reasoning about any wake-up call. Returns the current time in UTC, in the user's home zone, in the user's device zone (if known), and in any zones you pass. Use `now_local` of the TARGET zone to resolve words like 'tomorrow' or 'tonight'. Never compute dates from your own sense of the current time.

search_timezones read-only

Resolve a city, country, airport code, or partial zone name to IANA timezone identifiers. Returns ranked candidates with the current UTC offset. If more than one plausible candidate exists (e.g. 'Portland'), ask the user which one before scheduling.

list_wakeup_calls read-only

List the user's wake-up calls. Each has its next call (`next_occurrence`: the local time with its IANA zone and UTC offset, `scheduled_at` in UTC, the time in the user's home zone) and a `summary` sentence. Always say a time together with its zone, never a bare time. `status`: 'active' (default) lists the calls that still ring; 'all' adds finished and turned-off ones.

create_wakeup_call changes data

Create a wake-up call. `timezone` MUST be an IANA identifier (e.g. 'Asia/Tokyo'), never an abbreviation or offset; use `search_timezones` if unsure. For one-off calls provide `local_date` (resolved in the TARGET zone using `get_time_context`) or `in_minutes`. The response restates the call in the target zone and in the user's home zone; read it back to the user verbatim and mention any `notice`.

update_wakeup_call changes data

Change a wake-up call: pass `schedule_id` (from `list_wakeup_calls`) and only the fields to change, with the same rules as `create_wakeup_call`. A new `timezone` MUST be an IANA identifier, never an abbreviation or offset (use `search_timezones`); resolve a new `local_date` in the TARGET zone using `get_time_context`. The response restates the call in the target zone and in the user's home zone; read `confirmation_text` back to the user verbatim and mention any `notice`. Changing the time, date (or days) or zone of a call that is turned off or done turns it back on, unless you also pass `enabled: false`. To clear a recurring call's end date, pass `end_date: ""`. Turning on a one-off whose time has passed fails with `time_in_past`: ask the user for a new date.

cancel_wakeup_call changes data, can delete

Cancel a wake-up call. `mode` 'delete' removes it (the default for one-off calls); 'disable' turns it off so it can be turned back on later (the default for recurring calls). Read `confirmation_text` back to the user verbatim.

skip_next changes data

Skip only the next call of a recurring wake-up call; the days after it still ring. Returns the new next call with its zone. Read `confirmation_text` back to the user verbatim. To stop a one-off call, use `cancel_wakeup_call`.

pause_wakeup_call changes data

Pause a recurring wake-up call: no calls on local dates before `until`, which is a date (YYYY-MM-DD) in the call's own zone, resolved there using `get_time_context`; it rings again from `until`. Read `confirmation_text` back to the user verbatim.

resume_wakeup_call changes data

Resume a paused recurring wake-up call, so its next eligible day rings again. Read `confirmation_text` back to the user verbatim.

list_call_history read-only

The user's past wake-up calls, newest first: each with a `summary` in prose that names its zone and what happened (answered on which attempt and confirmed when, or why not).

get_account read-only

The user's account: name, home time zone, verified phone numbers (masked), plan and calls left, and whether calls are turned off. Calls turned off by pressing 9 can be turned back on only by the user, in the app or on the web, never through this assistant; phone numbers, billing, API keys and deleting the account are also managed there. Send the user to the app for those.

No arguments.

plan_trip_wakeups changes data

Set wake-up calls for a whole trip: one itinerary entry per call, each with `local_date`, `local_time` and `timezone` (an IANA identifier for where the user will be that morning; use `search_timezones` for each city, and resolve each date in that TARGET zone using `get_time_context`). Call it with `dry_run: true` (the default) first: it creates nothing and returns every entry resolved, with `scheduled_at`, the time in the user's home zone, any `notice`, and `conflicts` (calls already ringing that local day). Show that plan to the user, and only after they confirm call it again with `dry_run: false`, which creates every entry in one transaction (all or none). Read `confirmation_text` back to the user verbatim.

set_travel_wakeups

Set wake-up calls for a trip from an itinerary: resolve each city's zone, plan with a dry run, and create only after confirmation.

• itinerary_text required The trip in the user's words: dates, cities, wake-up times

morning_routine

Two recurring wake-up calls, one for weekdays and one for weekends, created after confirmation.

• weekday_time required Weekday wake-up time, 24-hour HH:MM
• weekend_time required Weekend wake-up time, 24-hour HH:MM
• timezone required IANA zone of the place the calls ring, e.g. America/New_York