[pull] main from UsefulSoftwareCo:main

.changeset/mcp-http-refusal.md

@@ -0,0 +1,5 @@
+---
+"executor": patch
+---
+
+**Fix: an MCP server refusing a tool call with a 4xx HTTP response (for example Stripe's `422` when `stripe_context` is missing) surfaced as `Internal tool error [id]`.** When the body is a JSON object naming the problem, the call now returns a typed `mcp_tool_error` failure with the server's message and status, so the model can fix the arguments instead of reading an outage.

.changeset/mcp-invocation-sdk-failure.md

@@ -0,0 +1,5 @@
+---
+"executor": patch
+---
+
+Name the MCP SDK rejection (error class and code) in the `Internal tool error` defect log, so an opaque MCP failure can be diagnosed from the trace instead of only naming the tool that failed.

.changeset/mcp-jsonrpc-refusal.md

@@ -0,0 +1,5 @@
+---
+"executor": patch
+---
+
+**Fix: an MCP server refusing a tool call with a JSON-RPC error (for example `-32602 Invalid params`) surfaced as `Internal tool error [id]`.** The server's answer is for the caller, so it now comes back as a typed `mcp_tool_error` failure carrying the server's message and JSON-RPC code, and the model can correct the arguments instead of reading an outage.

apps/cloud/src/edge/marketing.test.ts

@@ -20,6 +20,9 @@ describe("isMarketingPath", () => {
     "/blog/",
     "/blog/some-post",
     "/llms.txt",
+    "/index.md",
+    "/setup-prompt.md",
+    "/pricing.md",
     "/og-image.png",
     "/_astro/app.css",
     // The blog author card loads its avatar from marketing's public/authors;

apps/cloud/src/edge/marketing.ts

@@ -20,6 +20,9 @@ const MARKETING_PATHS = [
   "/google-workspace",
   "/blog",
   "/llms.txt",
+  "/index.md",
+  "/setup-prompt.md",
+  "/pricing.md",
   "/api/detect",
   "/_astro",
   "/authors",

apps/docs/docs.json

@@ -33,7 +33,7 @@
       },
       {
         "group": "Hosted",
-        "pages": ["hosted/cloud", "hosted/docker", "hosted/cloudflare", "hosted/tracing"]
+        "pages": ["hosted/cloud", "hosted/docker", "hosted/tracing"]
       },
       {
         "group": "Concepts",

apps/docs/index.mdx

@@ -14,7 +14,7 @@ Choose how to run Executor:
 - **[CLI](/local/cli)**: a background service on your machine, from the terminal
 - **[Desktop app](/local/desktop)**: the same runtime, as a desktop app
 - **[Executor Cloud](/hosted/cloud)**: hosted, with a free tier; nothing to run yourself
-- **Self-host**: your own infrastructure, via [Docker](/hosted/docker) or [Cloudflare](/hosted/cloudflare)
+- **Self-host**: your own infrastructure, via [Docker](/hosted/docker)
 
 ## Set up with your agent
 

apps/docs/mcp-proxy.mdx

@@ -52,7 +52,7 @@ Executor:
 
 - **Local:** see [CLI](/local/cli) for `executor mcp` and the `add-mcp` command.
 - **Hosted:** see [Executor Cloud](/hosted/cloud), or self-host on
-  [Docker](/hosted/docker) or [Cloudflare](/hosted/cloudflare).
+  [Docker](/hosted/docker).
 
 Once a client is connected, every integration you add to Executor appears in that
 agent automatically.

apps/marketing/public/llms.txt

@@ -11,7 +11,7 @@ How it works:
 - Set policies: decide whether each tool is always allowed, needs approval, or is blocked.
 - Use it from any MCP-compatible agent: one catalog of tools, shared across every client.
 
-Run it your way: local CLI, a desktop app, hosted Executor Cloud, or self-hosted on Docker or Cloudflare.
+Run it your way: local CLI, a desktop app, hosted Executor Cloud, or self-hosted on Docker.
 
 ## Docs
 
@@ -20,9 +20,17 @@ Run it your way: local CLI, a desktop app, hosted Executor Cloud, or self-hosted
 ## Product
 
 - [Website](https://executor.sh): product overview and getting started.
-- [Pricing](https://executor.sh/#pricing): plans for Executor Cloud.
+- [Pricing](https://executor.sh/pricing): plans for Executor Cloud.
 - [Install](https://executor.sh/#install): install the CLI and connect your first agent.
 
+## For agents
+
+Markdown representations of the pages above, for machines rather than browsers.
+
+- [/index.md](https://executor.sh/index.md): the homepage as Markdown — what Executor is, how it works, what you get, ways to run it, pricing, and FAQ.
+- [/setup-prompt.md](https://executor.sh/setup-prompt.md): a prompt to paste into a coding agent. It picks the right form of Executor, installs it, connects over MCP, and gets a first connection working.
+- [/pricing.md](https://executor.sh/pricing.md): the Executor Cloud plans as Markdown.
+
 ## Source
 
 - [GitHub](https://github.com/UsefulSoftwareCo/executor): source for the integration layer, plugins, and hosts.