Routine Run

com.routinerunPublished by routinerun.comOfficial publisherv1.0.2Updated Oct 24, 2026

Read, start and move the routines on your iPhone; suggest changes you approve on the phone.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant read, start and move the routines on your iPhone, and suggest routine changes you approve on the phone.

What you can do
Read your routines and their runs, answered live by the phone rather than a server copy, and read notes and values where you have allowed it for that assistant. Suggest new routines or changes to existing ones, which wait on the phone until you save them. Start, plan, pause and move runs immediately, with each action undone in one press. Use a separate no-sign-in endpoint to write a routine for someone who has not connected the app.
When to use it
Use it when you want an assistant to work with routines that live on your iPhone: reviewing what you have, drafting or adjusting routines for your approval, or starting and rearranging runs while you are away from the phone. The public endpoint suits writing a routine for someone who has not installed the app.
Requirements
A remote Streamable HTTP endpoint; no local package. The main endpoint requires OAuth 2.1 sign-in: a short code is shown and typed into Routine Run under Settings › Connections › Connect an assistant, and the phone approves the assistant. The phone must be reachable to answer reads, within about 20 seconds. A demo library is offered for trying it without the app.
Before you install
Reads depend on the phone answering; a phone that does not respond in about 20 seconds is reported as not answered. New routines and changes are suggestions held on the phone unless that assistant is set to save without asking. Starting, planning, pausing and moving runs take effect at once, though each can be undone. Notes and values are only read when Read notes and values is enabled for that assistant. Removing the connection in the app signs the assistant out immediately.

Installation

In SourceWeft

  1. Open Routine Run in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.routinerun%2Froutine-run/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "routine-run": {
      "type": "http",
      "url": "https://api.routinerun.com/mcp"
    }
  }
}

README

MCP

Two servers, both Streamable HTTP without sessions.

ServerSign-inFor
https://api.routinerun.com/mcpOAuth 2.1 — a code typed into the appYour own routines and runs
https://api.routinerun.com/mcp/publicnoneWriting a routine for somebody who has connected nothing, or has not got the app yet

There is no account. Signing in to the first shows a short code; the person types it into Routine Run under Settings › Connections › Connect an assistant, and the phone itself approves the assistant. Removing that connection in the app signs it out at once. The sign-in page also offers a demo library, for trying it without the app.

Every tool, what each does, and what the relay keeps: developers/api.md. How to add it to each assistant: routinerun.com/help/assistants.

What it will and will not do

  • Reads are answered by the phone, not by a copy on a server. A phone that does not answer in about 20 seconds is said to have not answered.
  • A new routine, or a change to one, is a suggestion: it waits on the phone until the person saves it, unless they have set that assistant to save without asking.
  • Starting, planning, pausing and moving runs happen at once, and each is undone with one press.
  • Notes and values are read only where the person has turned on Read notes and values for that assistant.

Registry entries

server.json and server-writer.json are the entries in the official MCP registry, as com.routinerun/routine-run and com.routinerun/routine-writer.

Source: mcp/README.md at commit 93a919b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.2LatestOct 24, 2026
  2. v1.0.1Oct 19, 2026
  3. v1.0.0Oct 14, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Routinerun integrations

Routine Run: write a routine

com.routinerunOfficial publisher

A remote MCP server that lets an assistant write a step-by-step routine and return a link that opens it in the Routine Run iPhone app for review.

Streamable HTTPWeb executable
Productivity & Workflow3 toolsOct 24, 2026