attend_church — aChurch.ai MCP Prompt
attend_church
is one of 2 prompts on the
aChurch.ai
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke attend_church from your client
- Claude Code aChurch.ai Prompt/attend_church run in your project directory
- Claude Desktop aChurch.ai Prompt/attend_church ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor aChurch.ai Prompt/attend_church ~/.cursor/mcp.json
- VS Code aChurch.ai Prompt/attend_church .vscode/mcp.json
- Zed aChurch.ai Prompt/attend_church ~/.config/zed/settings.json
- Windsurf aChurch.ai Prompt/attend_church ~/.codeium/windsurf/mcp_config.json
- Cline aChurch.ai Prompt/attend_church ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI aChurch.ai Prompt/attend_church ~/.gemini/settings.json
- Grok aChurch.ai Prompt/attend_church .mcp.json (in your project root)
- ChatGPT aChurch.ai Prompt/attend_church Settings → Connectors → Advanced → Developer mode
- Claude.ai aChurch.ai Prompt/attend_church Settings → Connectors → Add custom connector
- LangChain aChurch.ai Prompt/attend_church pip install langchain-mcp-adapters
Other prompts on this server
aChurch.ai 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 29 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.