break_the_seal — seal MCP Prompt

break_the_seal is one of 3 prompts on the seal MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke break_the_seal from your client

• Claude Code seal Prompt/break_the_seal run in your project directory
• Claude Desktop seal Prompt/break_the_seal ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor seal Prompt/break_the_seal ~/.cursor/mcp.json
• VS Code seal Prompt/break_the_seal .vscode/mcp.json
• Zed seal Prompt/break_the_seal ~/.config/zed/settings.json
• Windsurf seal Prompt/break_the_seal ~/.codeium/windsurf/mcp_config.json
• Cline seal Prompt/break_the_seal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI seal Prompt/break_the_seal ~/.gemini/settings.json
• Grok seal Prompt/break_the_seal .mcp.json (in your project root)
• ChatGPT seal Prompt/break_the_seal Settings → Connectors → Advanced → Developer mode
• Claude.ai seal Prompt/break_the_seal Settings → Connectors → Add custom connector
• LangChain seal Prompt/break_the_seal pip install langchain-mcp-adapters

Other prompts on this server

• investigate_my_decisions
• what_a_receipt_proves

seal also offers 4 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 24 September 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.