executive_summary — OnPage.dev MCP Prompt
executive_summary
is one of 14 prompts on the
OnPage.dev
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke executive_summary from your client
- Claude Code OnPage.dev Prompt/executive_summary run in your project directory
- Claude Desktop OnPage.dev Prompt/executive_summary ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OnPage.dev Prompt/executive_summary ~/.cursor/mcp.json
- VS Code OnPage.dev Prompt/executive_summary .vscode/mcp.json
- Zed OnPage.dev Prompt/executive_summary ~/.config/zed/settings.json
- Windsurf OnPage.dev Prompt/executive_summary ~/.codeium/windsurf/mcp_config.json
- Cline OnPage.dev Prompt/executive_summary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OnPage.dev Prompt/executive_summary ~/.gemini/settings.json
- Grok OnPage.dev Prompt/executive_summary .mcp.json (in your project root)
- ChatGPT OnPage.dev Prompt/executive_summary Settings → Connectors → Advanced → Developer mode
- Claude.ai OnPage.dev Prompt/executive_summary Settings → Connectors → Add custom connector
- LangChain OnPage.dev Prompt/executive_summary pip install langchain-mcp-adapters
Other prompts on this server
OnPage.dev also offers 3 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.