iPhone only · requires iOS 27 · waitlist

Let AI agents control your iPhone.

Q: Is this iPhone only?

Yes. iPhone only. Askew is built on iOS Shortcuts automations and App Intents. There is no Android version and none is planned. iPad is not a target for the initial release.

Q: Which iOS version do I need?

iOS 27 or later. Askew relies on the iOS 27 notification-triggered automation to wake a Shortcut on a locked phone. There is no fallback for iOS 26 or earlier, and the App Store minimum version will enforce this.

Askew is a relay that lets Claude, ChatGPT, Cursor or any MCP agent run Shortcuts on your locked iPhone. Calendar, Reminders, Notes, Contacts, Health, Photos, HomeKit — Apple's personal data has no server API; the only door is your phone. Your agent walks through it: run a Shortcut, get the result back, and receive what the phone sends on its own.

Join the waitlist See how it works

Works with Claude Code, ChatGPT, Codex, Cursor, n8n — anything that can load an MCP server. Not yet released.

One job, end to end: the connector seals it on your machine, the relay only routes the envelope, the phone opens it and runs a Shortcut. The result comes back the same way.

Works with

Any agent that can load an MCP server.

Askew ships as a local MCP server. If your agent can add one, it can use your iPhone. No SDK, no plugin, no browser extension.

Claude Code
Claude Desktop
ChatGPT · OpenAI Agents
Codex
Cursor
n8n
Any MCP client

Product names belong to their owners. Askew is not affiliated with or endorsed by them.

How it works

Three steps, then it's just conversation.

One line for the agent, one automation on the phone, ever. No daemon on your machine, no browser extension.

Connect your agent

Add the local Askew connector to your agent as an MCP server. Your agent gets tools like run, notify and inbox.

$ claude mcp add askew -s user -e ASKEW_CONNECTOR_KEY=akc_… -- npx -y askew-mcp

Install the dispatcher

Tap one link in the Askew app. A single Shortcuts automation lands on your iPhone. Flip its toggle on. That is the only automation you will ever set up.

Allow once, then forget it

The first run asks “Always Allow” on an unlocked phone. From then on jobs run on a locked phone, in one to two seconds, with no prompt.

One automation on the phone dispatches every recipe. Adding a recipe is a link tap; the automation never changes.

Setup

Set up in 3 minutes.

One app on the phone, one MCP server for the agent, one automation. The relay at api.askew.my is the default, so there is nothing to configure on the server side.

01Get the app and a connector key

Install the Askew app on your iPhone (iOS 27). It is not on the App Store yet — join the waitlist for the first TestFlight build. In the app: Settings → Register device → allow notifications → New connector → copy the key. It starts with akc_ and is shown once.

02Add the connector to your agent

The connector is the askew-mcp package on npm (Node 22 or later). Pick your agent:

Claude Code

claude mcp add askew -s user -e ASKEW_CONNECTOR_KEY=akc_… -- npx -y askew-mcp

Claude Desktop · Cursor · any MCP client

{
  "mcpServers": {
    "askew": {
      "command": "npx",
      "args": ["-y", "askew-mcp"],
      "env": { "ASKEW_CONNECTOR_KEY": "akc_…" }
    }
  }
}

Codex CLI

[mcp_servers.askew]
command = "npx"
args = ["-y", "askew-mcp"]
env = { ASKEW_CONNECTOR_KEY = "akc_…" }

The first run prints the connector fingerprint. Compare it with the fingerprint shown in the app's connector screen — that is the end-to-end key check, once.

03Install the dispatcher and say hello

In the app, Presets → Askew dispatcher → Install. Pick Shortcuts in the share sheet → Add Shortcut → open it and turn on the Automation toggle at the top. With the phone unlocked, run one test push from Settings → Checkup and tap “Always Allow” once. Then tell your agent:

“Add dentist Thursday 3pm to my phone calendar.”

Your agent now has 9 tools — askew_run, askew_notify, askew_inbox_wait and friends. Every recipe you add in Presets is a link tap; the automation never changes.

Use cases

Both directions.

The agent asks the phone, the phone tells the agent, and the agent shows you things on the lock screen.

Agent → phonePhone → agentAgent → you

Agent → phone

Put it in my calendar

Type “dentist Thursday 3pm” in chat. The event is created in Apple Calendar on your locked iPhone and the agent reads back “Added: Dentist · Thu 3:00 PM”.

Agent → phone

Reminders and Notes

Add, find and complete reminders. Create and search notes. The agent works with the apps you already use, not a copy of them.

Agent → phone

Receipt OCR

“Log the receipt I just photographed.” The phone runs text extraction on the latest photo and returns the text. The image never leaves the phone unless you say so.

Agent → phone

HomeKit scenes

Let the agent run “Good night” or “Leaving home”. Scenes execute on the phone with your existing HomeKit setup and permissions.

Phone → agent

Morning briefing when you actually wake up

Your Sleep Focus ends. The phone gathers today's calendar, open reminders and weather, and sends them to the agent. A briefing lands on your lock screen.

Phone → agent

Apple Pay purchase → expense log

Every Wallet transaction fires an automation with amount, merchant and card. The agent appends it to your ledger, sheet or Notion. Zero effort after the tap.

Phone → agent

Action button, Share sheet, voice memo

Hold the Action button and speak. Share an article or PDF from Safari. Send a voice memo. It all goes to the agent's inbox, and the answer comes back as a notification.

Agent → you

Notifications and a results box

Briefings, drafts and alerts arrive as real lock-screen notifications, mirrored to Apple Watch, with the full text kept in the app.

Privacy

End-to-end encrypted. We can't read it.

With the local connector, jobs and results are sealed on your machine and opened on your phone (HPKE). The relay only carries envelopes. You verify the pairing once with a short fingerprint in the app.

The relay sees	The relay never sees
That a job exists, which recipe it targets, timestamps, delivery status	The input you sent, the result the phone returned, attachments
An encrypted notification hint	The plaintext of any notification body
Your device's push token	Your calendar, reminders, notes, health or photos

A server-mediated connector mode (for agents that cannot run a local process) is possible, and in that mode the relay does see job contents. The app labels which mode you are in.

FAQ

Questions people ask first.

Is this iPhone only?

Yes. iPhone only. Askew is built on iOS Shortcuts automations and App Intents. There is no Android version and none is planned. iPad is not a target for the initial release.

Which iOS version do I need?

iOS 27 or later. Askew relies on the iOS 27 notification-triggered automation to wake a Shortcut on a locked phone. There is no fallback for iOS 26 or earlier, and the App Store minimum version will enforce this.

What does my agent need?

The ability to load an MCP server. That covers Claude Code, Codex, Cursor, n8n and most agent frameworks. The local connector is a small process the agent starts on demand. No background daemon, no websocket, no browser extension.

How many automations do I have to set up?

One, once. A single dispatcher automation handles every recipe. Installing a recipe is a link tap. The first time it runs you approve “Always Allow” once on an unlocked phone.

Does it work when the phone is locked?

Yes. Measured on a real device: push to result in one to two seconds with the phone locked, twenty consecutive runs without a prompt.

Can I self-host the relay?

Undecided. The relay is small and the connector is end-to-end encrypted, so a self-hosted option is on the table. Join the waitlist and tell us if that matters to you.

When does it ship, and what does it cost?

Not announced. We are on a waitlist while the app goes through real-device testing and App Store review. Pricing will be published before launch.

Waitlist

Get the first build.

Email only. We will write when there is a build to install. iPhone with iOS 27 required.