> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thefaithapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect AI Assistants

> Let an AI assistant look up permitted church information through a personal, read-only connection.

Connect Claude, ChatGPT, or Codex to TheFaithApp so you can ask questions about
your church's information without copying records into each conversation.
The connection uses your TheFaithApp staff sign-in and your church permissions.

The first release is **read-only**. An assistant can look up supported records
and summarize permitted information. It cannot send messages, change records,
publish content, or process payments through this connection.

## Before You Connect

* Use your own verified church administrator account, or a staff account with
  an assigned church permission group. Confirm that it can open the records
  you want to ask about.
* Your AI provider or workplace may require an administrator to allow custom
  connections.
* Use the connection only with an AI account approved by your church.
  Information returned to the assistant is shared with that provider under
  your account's terms and settings.

The production server address is:

```text theme={null}
https://api.thefaithapp.com/mcp
```

Ask your administrator for the staging address when evaluating an unreleased
deployment. The production address works after the MCP release is deployed.

## Connect Claude

In Claude, open **Customize > Connectors**, add a custom connector named
**TheFaithApp**, and enter the server address above. Choose OAuth sign-in and
**Register automatically** when Claude asks how to identify its OAuth client.
Sign in to TheFaithApp, review the access request, and approve it.

If you use a managed Claude organization, its owner may need to add the
connector first. Enable the connection in the conversation where you want to
use it. See [Claude's connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

## Connect ChatGPT

Open **Plugins**, select the plus button, and choose **Add custom MCP server**.
Enter **TheFaithApp** and its server address, configure OAuth authentication,
and complete the prompts to create the connection as a plugin. Sign in to
TheFaithApp and review the access request. In a new conversation, type `@`
and select the plugin. Workspace policies may limit this option.

See [OpenAI's connection instructions](https://developers.openai.com/plugins/deploy/connect-chatgpt).

## Connect Codex

Add **TheFaithApp** as a **Streamable HTTP** MCP server using the same address,
then choose **Authenticate** to complete TheFaithApp sign-in. Your technical
administrator can use the [MCP setup guide](https://docs.thefaithapp.com/api-reference/mcp.md) for CLI commands.
See [OpenAI's MCP instructions](https://learn.chatgpt.com/docs/extend/mcp).

## Check the Connected Church

Start with: **“Which church am I connected to, and what can you look up?”**
Check the church name before asking about records. The connection follows the
church attached to the signed-in staff account; a church name in your prompt
cannot switch it to another church.

Try **“Find upcoming events”** or **“Search our sermons for hope.”** Available
information depends on your staff permissions. Review the source links and
the assistant's answer before relying on it.

## Disconnect or Resolve Access Problems

Disconnect TheFaithApp in your AI application's connection settings when you
finish using it. To invalidate an existing authorization at TheFaithApp as
well, ask your platform administrator to revoke that MCP connection.

If a lookup is refused, check your church account and permissions. Missing
records may be outside the supported read-only areas or outside your access.
If sign-in loops or the server cannot be reached, share the error and AI client
name with [support@thefaithapp.com](mailto:support@thefaithapp.com). Never include
passwords, tokens, or private church records in that message.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.