agentavow_get_started — AgentAvow Trust MCP Prompt

agentavow_get_started is one of 1 prompt on the AgentAvow Trust MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke agentavow_get_started from your client

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

AgentAvow Trust also offers 1 resource — 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.