Church ChatHelp
Skip to Content
Church ChatHelp
Developers

AI assistants

Let Claude, Cursor or VS Code read and post in Church Chat as a bot.

Church Chat has an MCP server, so an AI assistant can use a bot to read and post in the chats that bot was added to. Its address is:

https://api.churchchat.tentmaking.com/api/mcp

The assistant acts as a bot, not as you. It reaches only the chats that bot was added to, it can’t see your direct messages, and what it posts appears under the bot’s name. Everyone using the same bot shares its chats and its name, so set up one bot for each job. Each tool makes one request to the API, under the same rules as any other.

Before you connect

What the bot can read goes to the AI service. Messages the assistant reads are sent to the company that runs it, under that company’s terms. Only add the bot to chats where that’s acceptable, and leave pastoral or other sensitive chats out.

Messages can try to instruct the assistant. Anyone who can post in a chat the bot reads can write something meant to mislead it. Keep the bot to chats you trust, choose Read-only when it doesn’t need to post, and review what the assistant wants to do before you approve it.

Set up a bot

  1. A church admin creates a bot under Settings → Developers, and creates an API token on it. The token is shown once.
  2. Someone who can add people to a chat adds the bot under Chat settings → Developers, choosing whether it can post or only read.

A new bot is in no chats, so the assistant finds nothing until step 2. See API tokens for more about tokens.

Connect your assistant

Use your token where it says ccb_....

Claude Code

claude mcp add --transport http church-chat https://api.churchchat.tentmaking.com/api/mcp \
  --header "Authorization: Bearer ccb_..."

Run /mcp inside Claude Code to check that it connected.

Cursor

Add this to ~/.cursor/mcp.json, and set CHURCH_CHAT_TOKEN in your environment:

{
  "mcpServers": {
    "church-chat": {
      "url": "https://api.churchchat.tentmaking.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:CHURCH_CHAT_TOKEN}"
      }
    }
  }
}

VS Code

Add this to .vscode/mcp.json. VS Code asks for the token the first time and stores it securely:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "church-chat-token",
      "description": "Church Chat API token",
      "password": true
    }
  ],
  "servers": {
    "church-chat": {
      "type": "http",
      "url": "https://api.churchchat.tentmaking.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:church-chat-token}"
      }
    }
  }
}

Claude Desktop

Claude Desktop connects through the mcp-remote package, which needs Node.js. Open Settings → Developer → Edit Config, add this, and restart the app:

{
  "mcpServers": {
    "church-chat": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.churchchat.tentmaking.com/api/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer ccb_..."
      }
    }
  }
}

Other assistants

Any assistant that supports MCP over HTTP and lets you set a request header can connect. Send Authorization: Bearer <API token>. Sign-in through OAuth isn’t available, so assistants that only offer that can’t connect yet.

What the assistant can do

ToolWhat it does
get_bot_accountSays which bot it’s connected as
list_bot_groupsLists the bot’s chats, with unread counts
get_groupGets one chat, and what the bot can do in it
list_group_datesLists the dates of a repeating chat
get_repeating_groupGets a repeating chat’s schedule and when its next date opens
list_group_membersLists who’s in a chat, if it allows that
list_group_botsLists the bots that can read a chat
list_messagesReads a chat’s messages, newest first
list_thread_repliesReads the replies in a thread
post_messagePosts a message or a thread reply
edit_messageChanges one of the bot’s messages
delete_messageDeletes one of the bot’s messages
add_reactionReacts to a message
remove_reactionRemoves one of the bot’s reactions

The tools' names say group and their inputs say channel, both meaning a chat, so a chat’s id goes in channel_id. A repeating chat also has a group_id that stays the same from date to date, which is what list_group_dates and get_repeating_group take. Files can’t be uploaded or downloaded through MCP. Use the API for those.

Tool calls count toward the same limit as the token’s API requests, 300 a minute.

Troubleshooting

You seeCheck
401, or it won’t connectThe token is complete, starts with ccb_, and hasn’t been revoked.
No chats or messagesThe bot has been added to the chat.
Posting is refusedThe bot was added with permission to post, and the chat allows it.
Origin not allowedThe assistant runs in a browser. Use a desktop or command-line assistant.

To disconnect an assistant, revoke its token. Access ends at once.

On this page