pre_transaction_check — agentra MCP Prompt

pre_transaction_check is one of 2 prompts on the agentra MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke pre_transaction_check from your client

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

Other prompts on this server

• onboard

agentra 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 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.