Recipe chains
Connect compatible recipes so each result becomes the next step’s input, with optional approval checkpoints.
Use it: Pro Tools → name workflow → add steps → RunOutcome-driven recipes, your own AI provider, live business data via MCP, and total privacy control. Connect Claude, OpenAI, OpenRouter, ZenMux, or a fully local Ollama model.
Every recipe is a structured workflow — inputs, steps, and a finished output — so you get answers, not another blank chat box.
Pre-built workflows for CEOs, CFOs, CTOs, CHROs and CMOs — board deck reviews, contract risk scans, investor emails, and more.
Connect internal tool servers over the Model Context Protocol. Ask a question — the AI routes it to the right tool and returns real numbers, not guesses.
Connect Claude, OpenAI, OpenRouter, ZenMux, or a local Ollama model. Switch providers per recipe — no lock-in, ever.
Sensitive material — HR, M&A, financials — can be routed to run entirely offline on your machine via Ollama. Tool-calling works locally too.
For spreadsheets, the AI writes a transformation script that runs locally on your full dataset — exact math, any file size.
Build custom workflows in a visual editor. Save reusable skills — your voice, your company context, your rubrics.
ExecPilot speaks the Model Context Protocol (MCP) — the open standard for connecting AI to tools. Point it at your internal reporting server and the AI stops guessing and starts querying.
"What were my earnings last quarter?"
Discovers get_earnings_report on your Finance MCP server and calls it with period: Q3-2025.
Your own system returns the rows — the AI never invents a number.
A plain-English summary on screen, and the full report one click away as .xlsx.
No prompt engineering required. Pick a recipe, add your content, get a finished result.
Add an API key or point to a local Ollama instance. Keys stay on your device.
Choose from built-in packs, a custom recipe, or just Ask ExecPilot Anything.
Paste text, capture a selection, drop in a file — or let MCP tools fetch live data.
A finished brief, email, table, or downloadable Excel file — ready to use.
Switch tabs to preview what's inside each role-specific pack.
Finds red flags, gaps, and the hardest questions a director will ask.
Turns market or competitor news into a threat/opportunity brief.
Drafts investor emails in your saved voice and tone.
Stress-tests a decision with the strongest opposing case.
Upload a PDF or XLSX for an instant variance analysis.
Flags liability, indemnity, and renewal clauses that need counsel review.
Ask for last quarter's numbers — pulled straight from your reporting server.
Cleans, merges, and recalculates spreadsheets — returns a real .xlsx.
Analyzes a vendor's security questionnaire for gaps.
Evaluates a technical proposal against your criteria.
Turns a raw incident log into a clean postmortem doc.
Flags scalability and security concerns in design docs.
Local-model-only by default — for HR matters that can't touch the cloud.
Diffs two policy versions and summarizes material changes.
Extracts themes and sentiment from open-text survey responses.
Drafts role descriptions consistent with your leveling framework.
Free-form requests, with live MCP tool-calling when servers are connected.
Turns anything into 3 bullets plus a recommendation.
Extracts owners and deadlines from raw meeting notes.
Summarizes a thread and drafts your reply in seconds.
Chain work, enforce output standards, compare models, verify evidence, and keep a decision trail—all from the Chrome side panel.
Connect compatible recipes so each result becomes the next step’s input, with optional approval checkpoints.
Use it: Pro Tools → name workflow → add steps → RunAsk the model to ground claims in numbered source passages, then click citations to inspect the supporting text.
Use it: open recipe → enable Evidence-backed outputInspect changed cells, added rows, and removed rows before approving the transformed workbook for download.
Use it: Code Transformer → run → review → approveDefine required sections or fields. ExecPilot validates the answer and makes one correction attempt when something is missing.
Use it: + New → Output contract → Save RecipeSave recommendations with alternatives, assumptions, risks, evidence, owner, deadline, and follow-up date.
Use it: run recipe → Save decision → Pro ToolsConsequential MCP actions such as sending, updating, deleting, publishing, or paying pause for explicit approval.
Use it: approve the server, tool, and arguments shownRun the same recipe and input through two configured providers and inspect the results side by side.
Use it: Pro Tools → Model comparisonSave prior recipe versions, restore them later, and test drafts against representative inputs and expected terms.
Use it: + New → Test input → Test draftMaintain reusable terminology, strategy, products, KPIs, and policy context, then apply it only when relevant.
Use it: Pro Tools → Company context → select in recipeDetected CSV, Markdown tables, and structured spreadsheet results render as readable tables with safe Excel downloads.
Use it: request a table or run a spreadsheet recipeTurn the current result or a saved decision into a branded board memo, decision paper, or presentation outline.
Use it: run recipe → Export executive reportUse Claude, OpenAI, OpenRouter, ZenMux, or local Ollama while keeping provider credentials on your device.
Use it: Providers → configure → SaveApproval gates, output contracts, evidence links, and before/after review keep people in charge of consequential work.
ExecPilot adds host-level controls around document Q&A and MCP tool use, reducing the chance that instructions hidden in a file or tool response can redirect the model or trigger an unintended action.
Extracted document passages, MCP definitions, and tool results are checked locally for instruction overrides, role impersonation, secret extraction, encoded payloads, and external-send patterns.
High-risk document passages and MCP results are withheld from the answering model. Users see a clear warning and the reason content was constrained.
No MCP tool is exposed automatically. Users select the exact servers and tools permitted for each run, keeping the model's action surface intentionally narrow.
Every MCP invocation pauses for confirmation showing the server, tool, risk context, and exact arguments. A changed call requires a new approval.
Tool arguments are validated against their declared JSON schema. Definitions, arguments, responses, and model-bound results are bounded to limit malformed or oversized payloads.
Once untrusted MCP output enters a run, subsequent proposals carry an elevated warning. Tool traces render as inert text so server-controlled markup cannot execute in the extension UI.
Ollama only. Zero network egress. HR, M&A, board materials.
Pre-vetted providers for internal, non-public material.
Any connected provider. Fast, low-cost, for public or low-sensitivity tasks.
Browsers block extensions from calling local services unless the service allows it. Ollama needs one environment variable — OLLAMA_ORIGINS — to accept requests from ExecPilot. Pick the option that suits you.
Sets the variable only for the current PowerShell window. Ollama accepts extension requests until you close that window or stop the server. Good for trying things out.
Keep this PowerShell window open while you use ExecPilot. When you close it, the setting is gone.
Sets the variable permanently for your Windows account. Survives reboots. No admin rights needed. Recommended for most people.
Then fully restart Ollama: right-click the Ollama icon in the system tray → Quit, and start it again (or reboot). New environment variables are only picked up on a fresh start.
Sets the variable system-wide for every user account on the machine. Requires an elevated (Administrator) PowerShell. Use this on shared workstations or when Ollama runs under a service account.
Then fully restart Ollama (tray → Quit → start again), or reboot the machine.
chrome-extension://* allows any browser extension on the machine to call your local Ollama. For a tighter setup, replace the wildcard with ExecPilot's exact extension ID, e.g. chrome-extension://abcdefghijklmnop… (find it at chrome://extensions).Verify it worked: open ExecPilot → Providers → Ollama should list your local models when you run any recipe. If you still see a CORS or connection error, confirm Ollama was fully restarted after setting the variable.
You pay your model provider directly. ExecPilot charges only for the product layer.
For trying ExecPilot with your own API keys.
For executives who run this daily.
Install ExecPilot, connect a model, and run your first recipe in under two minutes.
Add to Chrome — Free