Marketing: lead the hero with the MCP-gateway positioning#1089
Conversation
Add a hero subhead that says plainly what Executor is (an MCP gateway) and that anything speaking MCP connects to one endpoint and reaches every connected tool. The h1 alone left the mechanism ambiguous.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | 9424a09 | Commit Preview URL Branch Preview URL |
Jun 23 2026, 03:28 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | 9424a09 | Jun 23 2026, 03:29 AM |
Greptile SummaryThis PR adds a subtitle paragraph to the hero section of the marketing page, positioning Executor explicitly as an "MCP gateway" and naming MCP-compatible clients (Claude Code, Cursor, Codex) as concrete examples.
Confidence Score: 5/5Safe to merge — a copy-only addition of one The change touches only static marketing HTML: a new subtitle paragraph, a margin tweak on the h1, and renumbered stagger animation classes. All four rise steps (1–4) remain sequential after the renumber. There are no functional paths affected. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["h1 — 'Connect any agent to everything.' (rise-1)"] --> B
B["p — MCP gateway subhead (rise-2) [NEW]"] --> C
C["AnimatedBeamDemo card (rise-3, was rise-2)"] --> D
D["Hero CTA — For humans / For agents (rise-4)"]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A["h1 — 'Connect any agent to everything.' (rise-1)"] --> B
B["p — MCP gateway subhead (rise-2) [NEW]"] --> C
C["AnimatedBeamDemo card (rise-3, was rise-2)"] --> D
D["Hero CTA — For humans / For agents (rise-4)"]
Reviews (1): Last reviewed commit: "Marketing: lead the hero with the MCP-ga..." | Re-trigger Greptile |
Cloudflare previewTorn down — the PR is closed. |
The hero h1 ("Connect any agent to everything.") left the mechanism ambiguous. Add a subhead that says plainly what Executor is, an MCP gateway, and that anything speaking MCP (Claude Code, Cursor, Codex) points at one endpoint and reaches every connected tool.
Copy-only change to the hero section.