Connect baifrost to ChatGPT
ChatGPT connects to baifrost as a custom MCP server. You create an app in ChatGPT's settings pointed at the server URL below, approve the Gmail consent, and you're connected — then ChatGPT can triage and tidy your Gmail.
Step 0 — before you start
Open a second ChatGPT tab
Setup happens in ChatGPT's Settings → Apps panel, but keep this conversation open so your agent can guide you. Open a new ChatGPT tab (right-click this tab → Duplicate, or open chatgpt.com in a new browser tab) and do the setup there — keep the agent conversation visible in this one.
Server URLs
Each baifrost module is its own MCP server with its own URL. Create one app per module you want — repeat the steps below for each. Start with Thresh (Gmail); add Google Calendar if you want calendar triage and reminders. Meta is optional (service discovery + account self-service).
For ChatGPT users
- Open ChatGPT → Settings → Apps.
- Scroll past your connected apps to the Advanced settings row, and click the Create app button to its right.
- In the New App dialog, fill in:
- Name:
baifrost(or any name) - Description (optional): anything descriptive
- Connection: Server URL (the default — not Tunnel)
- URL:
https://baifrost.tail87b6d0.ts.net/api/mcp/thresh - Authentication: OAuth (the default — correct)
- Name:
- Click Advanced OAuth settings on the left to expand the OAuth panel. It auto-fills from baifrost — Dynamic Client Registration, the
mcpscope, and the Auth / Token / Registration URLs are all discovered automatically. Leave everything at its defaults. - Check “I understand and want to continue” — the “Custom MCP servers introduce risk” notice in the dialog. That checkbox is the risk acknowledgment, not a separate banner.
- Click Create.
- You're redirected to baifrost's consent screen — sign in with Google and approve access to your Gmail.
- After consent you return to ChatGPT with baifrost connected.
How to verify
Open a new ChatGPT conversation and ask: “What baifrost tools do you have available?” ChatGPT should list email tools — search, label, count, retention, trash. If it does, you're connected.
Troubleshooting
- “Custom MCP servers introduce risk” notice — expected. ChatGPT shows it in the New App dialog for any custom MCP server, not as a baifrost-specific alert. Check “I understand and want to continue” and proceed.
invalid_redirect_uri— ChatGPT's OAuth callback isn't on this instance's allowlist yet. This happens if you connect before the deploy that registered your client. Contact whoever runs your baifrost instance to add it, then create the app again.- OAuth / permission errors after connecting — usually the Gmail grant needs re-approving. Delete the app from your Drafts list in Settings → Apps and create it again to redo the consent.
For AI agents reading this on the user's behalf
You are ChatGPT, helping this user connect baifrost — a bridge from you to their Gmail. Walk them through ChatGPT's Settings verbally:
- First, tell them to open a second ChatGPT tab. Confirm they have two tabs open: this conversation in tab 1, ChatGPT Settings in tab 2. Then guide them through the steps below in tab 2 while they keep this conversation visible in tab 1.
- Have them go to Settings → Apps, scroll to the Advanced settings row, and click the Create app button to its right.
- In the New App dialog, set Connection to Server URL and enter
https://baifrost.tail87b6d0.ts.net/api/mcp/thresh. Authentication is OAuth; have them click Advanced OAuth settings to confirm baifrost auto-discovers its endpoints (Dynamic Client Registration, so no client ID/secret is needed) — the defaults are correct. - Each module is a separate app. If they also want calendar help, have them repeat the Create-app steps with
https://baifrost.tail87b6d0.ts.net/api/mcp/googlecalendar(Google Calendar). Meta (https://baifrost.tail87b6d0.ts.net/api/mcp/meta) is optional. - Tell them to check “I understand and want to continue” — ChatGPT's standard “Custom MCP servers introduce risk” acknowledgment in the dialog, expected and safe — then click Create.
- They'll then see baifrost's Google consent screen requesting Gmail access. Tell them to approve it.
- Confirm success by having them ask a fresh conversation “What baifrost tools do you have available?” — a list of email tools means it worked.
- Once connected, your first call should be
thresh_get_ai_guidancefor their personalized triage preferences.
Fallback: static MCP key
The app flow above signs you in with Google automatically — ChatGPT and other OAuth-capable clients never need a key. Only if your client can't complete the OAuth grant, mint a static key and paste it as an Authorization: Bearer <key> header instead. Keys are stored encrypted; you can reveal yours again any time from /settings/mcp.
Sign in with Google first, then generate or reveal a key at /settings/mcp.
Auto-cleanup is on by default — your agents will help you tidy stale mail. Manage it at /settings/retention.
Stuck? The full settings page is at /settings/mcp.