export_control_changes_brief — Scrutica MCP Prompt

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

by client

How to invoke export_control_changes_brief from your client

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

Other prompts on this server

• facility_brief
• verify_scrutica_number

Scrutica also offers 8 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.