Marketing Page V2

[mrzmyr]

Executor is code mode (ref1, ref2) + credential proxy.

Problem Statements

• MCPs are limited to the tools they expose (custom integration needed for GraphQL / CLI / REST)
• MCPs tools can be called one at a time (no parallelize, see video)
• MCPs return full payloads resulting in unnecessary token usage
• CLIs use full permissions (no limitation)
• Secrets are stored on hard drives (not encrypted vaults)

Solution Statements

• Unify the API interface into one MCP: access GraphQL, CLIs, REST APIs, MCPs
• Code mode can parallelize using Promise.all
• Code mode can return partial payloads (e.g. { count: tickets.length })
• Policies: define read and write permissions per source
• Integrate with macOS Keychain, 1Password for secure credential access

Layout

• Banner
  • last release link/relative date: proof its active
  • GitHub Link
  • Roadmap: link to github issue?
• Hero
  • interactive demo
  • logos of agents it integrates with (e.g. claude code, open code etc)
• Features: based on comparison, see problem / solution statements
  • access: show supported sources -> link to sources registry
  • fast: code mode parallelize
  • cost: use partial payloads
  • security: policies, 1password
  • Advanced
    • use executor with executor
    • use SDK
• Usage
  • socials proof?
• Recent Releases
• CTA

Demo above the fold is the way to go (cursor.com, linear.app):

1. User selects popular source and authenticates
2. Adds to agent
3. Agent runs
4. Agent shows results

[mrzmyr]

@RhysSullivan I think the demo is not specific enough to the problem statement yet. The demo could be the same for others. Any idea how to convey the idea of code mode more in the demo?

Maybe multiple demos:

1. simple
2. block writes
3. SDK

Would also be good to know where you disagree / agree on features to highlight. Maybe I'm missing some here.