audit_evidence_claims — Agenda Intelligence MD MCP Prompt

audit_evidence_claims is one of 3 prompts on the Agenda Intelligence MD MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke audit_evidence_claims from your client

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

Other prompts on this server

• draft_evidence_memo
• self_correct_packet

Agenda Intelligence MD also offers 6 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.