Built by your agents. Run by Executor.

Bring your own agents. Build tools, automations, and apps once. Run them on Executor and use them across all your agents.

Get started

Rather keep it on your machine? Desktop, CLI, or self-hosted ↓

Start with something useful.

Bring a tool you already use, give your agent a skill, or ask it to build something you wish existed. Start small. You can change it as you go.

An existing tool

Bring an MCP or API you already use.

A skill

Teach your agents how you like things done.

Something new

Describe it. Your agent writes the code.

Ask for what you actually need.

Executor is not an agent. It’s a place for your agent to build and run software.

Ask your agent

“Pull together my signups and open issues. Give my agents one way to check what's changed.”

Your agent builds a reusable tool and deploys it to Executor.

Daily briefDeployed

Uses your accounts

PostHogGitHub

A tool your agents can call

daily_brief.get_changes()

Signups and open issues, compared with the last check.

Build it with one agent. Use it and change it with another.

Let it keep working.

Give that tool a schedule. Keep a history of what it finds. Add a page you can open. Executor runs the app, even after the conversation ends.

You

Run this every weekday at 9. Save the results and build me a page to read them.

Daily briefYour app
Weekdays at 09:00
Monday · 09:01Latest report

A strong start to the week.

New signups

1,284

+12% from last report

Open issues264 fewer than last time

Signups are up 12%, and there are four fewer open issues. Organic search brought in the most new users.

✓ Read PostHog + GitHub✓ Write brief✓ Save report
Your app keeps running. Your data stays with it.Example data

That's an Executor app.

A tool your agent can call. An automation that runs on its own. An interface you can use. They can all be parts of the same app, built around what you need.

Tools

Call anything, it's just JavaScript.

Skills

Give your agent instructions it can use again.

UI

A page for your app, at its own URL.

Storage

Keep data and state between runs.

Triggers

Run on a schedule or respond to webhooks.

Workflows

Durable work across multiple steps.

It's just code

And you don't have to write it

index.ts16 lines
import { defineApp } from "apps";
import { github } from "./providers";
import { database } from "./database";
import { listBriefs, saveBrief, refreshBrief } from "./tools";
import { refresh } from "./workflows";

export const requirements = {
  accounts: { github },
  database,
};

export default defineApp(requirements, {
  queries: { listBriefs },
  mutations: { saveBrief, refreshBrief },
  workflows: { refresh },
});

The entry point

Brings the accounts, data, tools, and workflows together in one app.

One app. Ordinary files.Choose a file to look inside.

Run it where you want

Use Executor Cloud, or run the same setup on your own machine or server.

CloudDeploy your apps. We handle the hosting.Deploy an app
DesktopRun Executor on your computer, with local apps and private app pages.Download for MacDownload for Mac (Intel)Download for WindowsDownload for Linux
CLIRun the local server from your terminal.npm i -g executor
Self-hostedRun the hosted server on infrastructure you control.Self-hosting docs

What people say

From people using Executor to connect their agents to their tools.

Wilson Wilson@euboidI disconnected all my MCPs and switched to executor.sh. Best thing I've done this year. Claude, Codex, Hermes, Grok, Cursor - it's so much overhead remembering where you've connected what. Now I just have one MCP - and all my agents inherit all my tools. Highly recommend!Aiden Bai@aidenybaiexecutor is very good softwareDrake Thomsen@ThomsenDrakeMoving my connectors onto executor.sh is such a refreshing experience. I now only have to configure a single connector when I'm setting up a new agent instead of 15 different OAuths or API keysDaniel Lockyer@DanielLockyerI've been using Executor since this mini-pitch and honestly it's great. I just configure my MCPs/OpenAPIs in one place and all my clients can use the connections. I've also used the blocklist feature to remove dangerous actions from some MCPs, very nice. Can recommend!Hegar@hegargarciaholy shit this is so good! takes a little to setup but this is the right primitive for MCPs! just the facts you can hook up different Google accounts and it’s just mile better than any of the labs or harness out there 😭Ryan Morrissey@ryan_morrExecutor is awesome and has solved so many problems for us. Most of our prompts for hermes nowadays include the words "use executor" or "can you use executor". One of the few products I find myself recommending to people dailyKaeden@kaeden_devI was thinking about building some custom Effect-based MCPs like you did with YNAB, until I realized that Executor already did everything I wanted. It's been incredibly useful.Anthony Kroeger@kr0derwait executor might be one of the best things ever made for AI agentsZaher@zahergI can't express how much I enjoy having Executor added to my toolset. there are many projects, but this one is something I can see myself keep usingchris jayden@itschrisjaydenI underestimated executor.sh, it's amazing! I run it locally on my mac mini, and my other devices just pull from it, amazing!shuv@shuv1337executor.sh is excellent. i have to admit, i spent way too much time forking, integrating and maintaining pieces of it in my own project and hadn't used it 'as is' in a while. it's become very good so i'm back to just running local executor now. great work!Mrigank Krishan@zevtnaxI'm using executor.sh for this - been great so far!Ryan Morrissey@ryan_morrIt's truly a stellar product we use it everydaymteam.gwei@mteamisloadingSet up Executor Cloud today to give my cloud agents access to all my accounts from one plane. Great experience! Well doneAxel@Swedish_chefExecutor makes it so incredibly easy for end usersJeremy Osih@jeremyosihexecutor is soo good, thx for everything !George Kontridze@georgekontridzeExecutor is also greatFlorian Bühringer@capeflowCloudflare artifacts + executor.sh with agent-native skill authoring. Centralized - shared - instantly updated across the team (as it's behind execute). Works like a charmSami Laakkonen@samilaabe me. setting up openclaws for my team. access & integration hell. 1h later demo of Executor from Rhys. problem solvedYahia Bakour@mynameisyahiaCheck out Executor! A really novel approach to orchestrating tool calls for agents without blowing up your context window with provider-specific semantics. Feels obvious in hindsightBrandon Ravion@flybayerexecutor.sh to get code mode for any API or MCPErik Rogne@erikrogneFinally. This is a great idea
Add yourson XUsing Executor? Post about it and tag @executorsh. We read every one.Nate Berkopec@nateberkopecFor the last 3 months I've been telling all my clients to move everything to MCPs and executor.sh.Christoffer Bjelke@chribjelupdate: it *is* the perfect wrapper. now executor.sh is my only mcp for all my agents, and i just configure my other connected services through executor. all integrations can have multiple connections, so i can have personal/work accounts for every integration. so so nice, literally perfectNathan Flurry@NathanFlurryreally digging executor + browserbase for unifying my integrations. i use agents in a lot of places: linux rig over ssh, amp orbs for bg agents, claude/chatgpt on mobile. this setup lets me sign in once (browser or mcp) and access it everywhereJosXa@JosXa_I compared dozens of MCP aggregators and we finally have a winner. Executor is going to become a standard, I can smell itSherlock@thesherlockerOkay, this is really cool, I don't know why I've delayed my adoption so much. Executor is now my defaultJohn Yeo@johnyeo_executor is the one tool we were looking for to unify our MCP servers across our team, we all use it daily nowshuv@shuv1337executor is so good. i have limited toolkits deployed to my whole team via grok bot enterprise, plus a much more robust set of tools for myself/my clankers. it's incredibly usefulKyle Finken@KyleFinkenIncredibly surprised i haven't seen more people talking about poke + executor. By far the best experience for personal agent integrations rnAndre Landgraf@andrelandgrafDef check out Executor! I use it primarily for code mode across a few REST APIs and MCP servers. So nice when you'd otherwise have to run thousands of tool calls across meetup RSVP reviews etcjoel@jwwweldamn executor.sh is so goated. i can really bring my favourite mcps to whatever harness without needing to set it up again, so nice!!brandon@branalytcfinally setup executor.sh and it's working great! happy to finally have a unified mcp!!jan@miaugladiator1can vouch, been using it for like a month and its so peakWill Undrell@WillUndrllCongrats bro! I'm a huge fan of Executor, I use it exclusively now and it works a dream!Jacob Hands@jachandsBtw executor is fantasticAlex Rigler@alexriglerFolks should really take a look at Executor. It is awesome and a great codebase tooRamón Medrano Llamas@rmedranollamasexecutor may be a masterstroke now that it clicked on meZaher@zahergall I had to do is to add it as integration to my executor, and now I have access to it as mcp without deploying any MCPSaatvik@aryasaatvikone of my favorite use cases for executor.sh codemode is great for correlating across multiple sources and tools and you can reuse auth across all agentsJose Mejias@MejiasDevPi + Herdr + Collie + Executor is unbeaten. Is not even close.Raduan Al-Shedivat@0xRaduanall problems of MCPs are solved with executorBen Patton@benapattonWhat are we doing people?! Just use executor.sh or find an alternative.
Malte Ubl@cramforceI've been working on integrating Rhys's excellent `executor` package into just-bash.Ethan Niser@ethanniserI dont think I've ever oauthed so much in my life until AI. connections, connections, connections. s/o executor.shSam Hogan@samhoganMy favorite features: Quick set-up. Easily share MCPs between agent harnesses with centralized authentication and access control. Auth once, use everywhere. Codemode execution by defaultBen Davis@davis7Really like what Rhys is working on with executor. I think it or something like it is probably the futureBence Redmond@BenceRedmondThe use case for Executor is obvious to anyone who's had to manage MCP servers across Claude Code/Codex/Hermes/etc. Incredibly useful, and resolves so many frustrations that I've had with agent configs over the past few months. The product roadmap is also super exciting!Phil Zona@philzonaFinally trying executor.sh and I get why people like it so much. Setup was extremely simple relative to what it actually does. Its concept of "toolkits" is cool too. Very very impressed so farSerge@sergicalvery much enjoying Executor. configure different connections for the same MCP: I have a work and a personal Cloudflare account so I don't need to re-auth into different ones. manage all the connections between different clients. 1Password to manage secrets instead of storing them in plain text. really well doneSomto@somto_oderaMoved all of my MCP tooling to executor.sh - self deployed and tbh, its delightful not worrying about setup on my local or VM - one interface and everything is availableJames Brock@JamieBrock19060I've installed and configured Executor with my Claude and Codex. The three of us love it. Been able to cull so many tools loading at session launch. App is being updated like crazy. Interesting to see where this goes!Corey Haines@coreyhainescoReally liking executor.sh to make it easy to port agent integrations across platforms.blueguy@itsmeblueguyAnd executor.sh is all about MCPs eheh. Btw, been using it and loving :DSH@RocketmanShYep it's perfect!Ian@IanMitchel1Been hard with a baby but I've been trying to consciously spend more time using and learning different AI tools. I can't even imagine doing this without Executor. How did you all live like that?adam ghaida@adamghaidathanks rhys :)) executor has definitely been incredibly powerful for our users and also a joy hereGriffin@grfwingsExecutor is a great tool, please give it a try!sensho@senshoWE all love executorOliur@UltraLinxWhilst setting this up I kinda realised a lot of apps don't have MCP gateways, so I ended up having Claude build the MCPs for me and host it on the same VPS as Executor. HUGE time saver. And I can choose which MCPs to share with my team or keep them private.Anthony Kroeger@kr0derwe're saved, add this to Claude Code/Cursor ASAP via Executor. both are lacking computer use at the moment so this is super useful since i use bothDillon Mulroy@dillon_mulroyself hosted executor - no more managing a bunch of disparate mcp serversNathan Flurry@NathanFlurrytldr why i'm excited for executor/integrations: everyone needs a "company brain". everyone thinks memory is the issue. but nobody gets past the integrations phase. tackle integrations first, everything else comes later. and most importantly oss + self-hostableAidan Sunbury@aidansunburyWe use Executor for MCP access, tailscale aperture for inference access, infisical for secret access

Good company.

64 notes from people using Executor.

Pricing

Cloud is free for up to three people. Team is $15 per member per month. Running it yourself is free.

See pricing ↗ · Talk to us about Enterprise

Writing

About

Deploying an app for your agent should be as simple as deploying a website. Executor is where your personal software lives.

Rhys SullivanFounder. Tweet your feedback at me, RhysSullivan

Discord ↗