How to use FaithGPT with Perplexity and the Comet browser
TL;DR: Comet is Perplexity's free Chromium browser, and its sidebar assistant reads the page you have open and acts inside your logged-in session. That makes the reliable setup simple: sign in to faithgpt.io, let the sidebar handle the clerical work across the Bible reader, verse finder, and prayer journal, and send the actual Scripture questions to FaithGPT, whose answers are checked against a reference corpus with published citation accuracy. Perplexity Pro, Max, and Enterprise accounts can also add FaithGPT's MCP server at https://api.faithgpt.io/mcp under Connectors, signing in with a FaithGPT account to get five tools for Scripture lookup, topical verse search, grounded answers, doctrine review, and devotionals. Whether those connectors appear in the Comet sidebar specifically is unconfirmed, so check Perplexity's help center. You cannot wire Perplexity's OpenAI-compatible endpoint to FaithGPT's API; that compatibility layer only calls Perplexity's own models.
Open Romans 9 in FaithGPT's Bible reader. Ask the Comet sidebar to summarize the chapter's argument. You will get back a clean paragraph about election and mercy that reads like it came out of a study Bible. Now open a second tab, paste that paragraph into FaithGPT's chat, and ask whether the summary survives contact with the actual text.
The second answer is the one I keep. The sidebar summarized what was on the screen using whatever it picked up from the open web. FaithGPT checked its answer against the reference corpus that comes with every account, and we publish how often those citations land where they claim to.
That gap is the whole pattern. Comet moves you around and does the clerical work. FaithGPT answers the Scripture questions. Get the division of labor right and the two of them are genuinely useful together. Get it backwards and you have an expensive way to read summaries of summaries.
What Comet actually is
Comet is Perplexity's browser. It is free, and it runs on Chromium, so for everyday purposes it behaves like Chrome.
The part that matters here is the sidebar. Perplexity's assistant sits next to the page, reads what is currently on your screen, and acts inside your signed-in session. It clicks, it types into fields, it moves between tabs, it pulls text out of a page you are already authenticated on. There is no API key to paste and no config file to write. You log in to a site the normal way, and the sidebar can work inside it.
That property is why this is worth writing about. faithgpt.io is a real web application rather than a brochure. Chat, the Bible reader, verse finder, prayer journal, daily devotionals. Anything you can do there with a mouse, the sidebar can help you do with a sentence.
Path one: point the sidebar at faithgpt.io
This is the path that works today, needs nothing beyond a login, and does not depend on any feature I have to hedge about.
Sign in at faithgpt.io . Open whatever you are actually studying, usually the Bible reader . Open the Comet sidebar. Then treat the sidebar as a fast pair of hands rather than as a teacher.
Prompts that work well, because they are about the page rather than about theology:
"List every verse on this page that uses the word righteousness, with references."
"Open Romans 10 and Romans 11 in new tabs so I can move between them."
"Copy the reflection I just wrote in the prayer journal and fix the typos. Do not change my wording."
"Group the last twenty prayer journal entries by theme and tell me which ones I marked answered."
"In the FaithGPT chat tab, ask what Paul means by vessels of mercy in Romans 9:23, and tell it to cite the verses."
That last prompt is the move. You are using the sidebar as a typist and letting FaithGPT do the answering.
Ask the sidebar directly what 1 Corinthians 11:10 means and it answers from the open web, which contains every reading anyone has ever published, ranked by whoever won at SEO. Ask FaithGPT the same question and the answer is checked against a reference corpus included on every plan, with citations you can click through to the verse in the reader and read in context.
The failure mode here is quiet, which is what makes it worth naming. A general assistant rarely says something obviously wrong about a contested verse. It says something confident and unsourced, drawn from whichever interpretation happened to be loudest in its training data, and it sounds exactly as certain on a verse the church has argued about for four centuries as on John 3:16. You have no way to tell those two cases apart from the prose alone. A citation you can open is how you tell.
There is a smaller reason too, and it compounds over months. A sidebar conversation is a panel that goes away. FaithGPT conversations live in your account, so the study you did in March is still there in September when the same passage comes back around in your reading plan.
The sidebar is also genuinely good on the surfaces that have nothing to do with interpretation. Point it at the verse finder and ask it to run three phrasings of the same search and collect what each one returned. Point it at the prayer journal and ask it to find every entry mentioning a person by name. That is real work, and it is work no amount of Scripture grounding would help with.
Path two: FaithGPT as a Perplexity connector
Perplexity added custom remote MCP connectors in March 2026 for Pro, Max, and Enterprise accounts. You add one from account settings, under Connectors. Paste a server URL, and Perplexity walks you through signing in.
FaithGPT's server address is:
The sign-in step is OAuth against your existing FaithGPT account, which is what ties the tools to your credits and your data rather than to some anonymous shared pool.
Once it connects, Perplexity gets five FaithGPT tools:
lookup_scripture returns the exact text of a reference you supply, in KJV, ASV, or YLT.find_scripture_by_topic handles the case where you have a theme or a life situation but no reference in hand, and returns verses with a short explanation.ask_faithgpt gives a Scripture-rooted answer with Bible citations attached.review_doctrine takes a sermon excerpt, an article, or a bare theological claim and tells you whether it handles the text responsibly. It is guidance, and it does not replace a pastor.create_devotional writes a title, passage, reflection, and prayer around a theme you name. It hands you the text and saves nothing.
Now the honest part. Perplexity documents custom connectors as a feature of its assistant. I have not been able to confirm that they surface inside the Comet sidebar specifically, and I would rather say so than send you hunting through a settings menu for twenty minutes. Check Perplexity's help center for the current answer before you build a routine around it.
If connectors do appear in your sidebar, you get both paths in one place: the assistant drives the page and calls FaithGPT's tools in the same conversation. If they do not, path one still works exactly as described, and path one was always the one that needed nothing.
What not to expect
You cannot point Perplexity at FaithGPT's model. FaithGPT publishes an OpenAI-compatible REST API at /api , and Perplexity publishes an OpenAI-compatible endpoint of its own, so people reasonably assume the two snap together. They do not. Perplexity's compatibility layer exists so your code can call Perplexity's models using an OpenAI client library. It does not accept a third-party base URL. If you want FaithGPT answering inside your own software, call FaithGPT's API directly and skip the middleman.
The connector needs a paid Perplexity plan. Comet itself is free, and path one works on a free Perplexity account, because path one is just a browser assistant operating a website you are logged in to. Custom connectors sit behind Pro, Max, and Enterprise. If you are on the free tier, nothing in path two is available to you, and nothing in path one is missing.
Tool calls spend credits. Every MCP call runs real FaithGPT work against your account, so an afternoon of heavy research draws your balance down the way the web app does. Plans and limits live at /pricing .
One caution worth a sentence, without the doom. Any browser assistant acts inside every session you are signed in to, which means a page carrying instructions buried in its text can try to talk it into doing something you did not ask for. Watch what it does when it is working across tabs you did not open yourself, and read before you approve anything that sends or saves.
Routines that survive a real week
The morning devotional, examined
Open your devotional on faithgpt.io and ask the sidebar to restate it as a list of the claims it is making. There are usually two or three, and one of them is usually doing more work than you noticed. Take that one to FaithGPT and ask what Scripture supports it. The whole thing runs about four minutes and puts a real gap between a devotional you agreed with and one you thought about.
Sermon prep with a verification stop
You are eleven tabs deep: a commentary, two blog posts, a lexicon entry, somebody's denominational position paper. Let the sidebar pull the argument out of each tab and stack them where you can see them side by side. Then stop, move to FaithGPT, and run the strongest claim from each source through chat, or through review_doctrine if you have the connector working. Tabs are for gathering. FaithGPT is the checkpoint everything passes through before it reaches a pulpit.
Month-end prayer journal
Ask the sidebar to group your entries by theme and flag the ones you marked answered. This is filing, and the sidebar is good at filing inside a page you are signed in to. What comes out is a list you can pray through instead of a scroll you keep meaning to reread.
Where to start
Download Comet, sign in at faithgpt.io , and open the reader to whatever passage you are in this week. Give the sidebar something small to prove it works, like finding every occurrence of a word on the page. Then ask FaithGPT what that word means in that context.
Read the two answers next to each other. One is a fast, competent summary of what was on your screen. The other cites verses you can open. That comparison takes ninety seconds and settles the question of which tool belongs on which job better than any article can.
If you are on Perplexity Pro, Max, or Enterprise, add https://api.faithgpt.io/mcp under Connectors and sign in with your FaithGPT account while you are at it. And if it turns up in the Comet sidebar for you, we would genuinely like to hear about it.
Helpful Scripture resources
Contact & support
Email the FaithGPT team at hello@faithgpt.io or visit the contact page .
Explore FaithGPT
