Add Atlas to ChatGPT
First follow your account-selected setup route. For URL sign-in:
- In ChatGPT, open Plugins → + → Add custom MCP server. Use the server URL
https://zs-macbook-pro.tail84283f.ts.net/mcpand choose OAuth. - Sign in with your invited Atlas account and allow access. URL sign-in needs no client ID or secret; for a preregistered client, follow your adviser's separate setup instructions.
- In a new chat, ask “Which business am I connected to?” and check the answer is your business.
If those controls are unavailable, ask your adviser for help. If your account offers Plugins → Upload plugin, you can instead download the Atlas connector and select atlas-connector.zip.
Your first useful session with Atlas
Atlas brings connected business records into ChatGPT. Start with the Atlas connection; three optional skills can be added later. Your adviser helps set up your company, provider connections and service access. This pilot uses assisted setup; confirm the service term in your account and agreed order.
Source update in progress: this guide describes Atlas's Composio-first cutover; publication of this text does not confirm deployment or acceptance. Jobber keeps its dedicated tools. QuickBooks and other providers use dynamic Composio capability search, schema inspection and generic execution. Restricted Platform reads use normal Atlas read access through atlas_gateway_read, with saved results available through atlas_gateway_read_result. The read-policy contract is verified on one Gmail sample; your adviser must confirm deployment and a useful task for your account before calling the client route ready.
1. Sign in to Atlas
For your first visit, open the private invitation from your Atlas adviser. Choose Continue with Google using the invited email, or sign in with that email and your existing Atlas password. If neither works, contact your adviser. The invitation connects your sign-in to the company Atlas prepared. It expires within seven days; ask your adviser to replace an expired link while keeping the existing setup. After joining, return through your Atlas workspace. Use the same sign-in when ChatGPT asks you to connect Atlas Innovations. Creating another login will not repair an existing assignment.
If Atlas asks you to verify your invited email, check that address’s inbox and spam folder and follow the verification link. If no message arrives, ask your Atlas adviser to resend it and check delivery. Then reopen your original invitation and sign in again. Atlas keeps the invitation unused until verification succeeds; signing in repeatedly does not verify the address.
Atlas handles the technical preparation: your company workspace, your client-owned Jobber developer app, and the Composio project and connections agreed for your business. You do not need to create a separate Auth0 developer account or manage a Composio dashboard. Your Atlas sign-in is separate from your existing Jobber or QuickBooks login.
2. Approve your business connections
Your workspace shows one next step. When Jobber is ready, select Connect, sign in to your business's Jobber account and approve access. Check the returned business name and account ID. You do not need to look up a Jobber account ID before connecting. If the page says Atlas is preparing your connection, your adviser still has work to do; no repeated login is needed.
Your adviser creates an app in your Jobber Developer Center, registers the Atlas callback, and saves its Client ID and Client Secret using the protected setup tools or operator import. Those credentials are encrypted and never redisplayed. They never belong in a ChatGPT conversation or the ChatGPT OAuth fields. Reconnects use the same verified Jobber business. Your adviser can replace the app's Client Secret without disturbing the connection; switching to a different developer app is possible only while Jobber is disconnected or needs reconnection.
The Jobber card also shows the authorizing user’s role when the connection was verified. It is a record of that connection, not a live permissions check. Older connections may say Not recorded and remain usable. The Atlas company owner can use Reconnect to refresh it.
QuickBooks and other agreed sources are separate authorizations. They are optional for a Jobber-only start. For QuickBooks, confirm the company ID with your adviser and select the matching company and environment. Tell your adviser if any returned identity is wrong. Atlas also activates the agreed access term; an inactive service is a separate issue from a provider connection.
3. Connect ChatGPT and prove it works
Open ChatGPT setup in your workspace. Your adviser prepares the Atlas app or plugin using the installation route available to your ChatGPT account or workspace. Sign in to Atlas Innovations with the same account used in step 1 and approve the connection.
Review the account and requested access before approving. Depending on your agreed setup, the connection may ask to:
- Read business data: retrieve Atlas context, Jobber records and permitted restricted Platform reads. This read route does not require business-change permission or approval of each read.
- Save Atlas content: save company context and feedback you ask Atlas to save, when sharing is enabled. Review the proposed content first.
- Make business changes: prepare and run supported changes under your company's write policy and exact in-chat approval. Connecting ChatGPT does not enable auto-run or approve an individual change. If you already enabled Jobber auto-run, eligible low-risk Jobber changes can run without another approval. Other Composio execution capabilities follow their exact approval path, including any read requested through a full-capability helper.
- Stay connected: refresh your Atlas sign-in between chats, subject to session expiry.
Each business account asks for its own permissions separately. Atlas permission does not replace Jobber, QuickBooks or Google authorization. For Gmail, Google's compose permission includes sending at the provider level. Review whether the selected generic action saves a draft or sends mail; a request for a draft does not authorize sending. If the account or access is unexpected, return to your adviser before approving.
Follow the route shown in ChatGPT setup in your workspace before downloading or installing a connector. If Atlas still needs to confirm your connection setup, ask your adviser to finish that step first. When your workspace shows URL sign-in, open Plugins → + → Add custom MCP server if your ChatGPT account exposes it, enter the Atlas server URL shown in your workspace, and choose OAuth. If those controls are unavailable, ask your adviser to check your account's installation route. The Add Atlas to ChatGPT section at the top of this guide also offers a connector download for accounts with Upload plugin. ChatGPT registers itself, so there is no client ID or secret to enter. For a company set up on the earlier manual route, Atlas staff supply the Atlas MCP URL and the registered Atlas ChatGPT OAuth Client ID, and verify the registered token authentication method and exact callback URL displayed by ChatGPT. Confidential clients using client_secret_post or client_secret_basic need the matching Atlas Client Secret; public clients using none must leave the secret empty. These are different from your Jobber app credentials. They are entered only into ChatGPT's OAuth configuration fields during assisted setup, never into chat. A plugin ZIP or a saved skill does not fix an OAuth connection failure.
Start a new conversation, enable Atlas, and ask:
Check my Atlas company and connection status. Read my connected Jobber business name and ID. Do not change or save anything.
Check that the business is yours. Then ask for one known customer and verify a real record. If QuickBooks is requested, separately verify its company ID and environment through the available generic gateway path. A connection card does not prove a read can run. Use the restricted Platform read route when permitted; other execution needs exact approval. The Gmail policy sample is not acceptance of your QuickBooks task. A connected provider card alone does not prove that ChatGPT works; this real result is the final installation check.
Return to your Atlas workspace and refresh. When the page offers Confirm my ChatGPT check, confirm only after checking your business and a known customer yourself. Atlas saves your progress so you can leave and resume. A changed connection or access term may require another check. This records your confirmation; Atlas cannot inspect your chat history.
Initial MCP onboarding can be completed with skills deferred. If you choose to add skills later, your adviser installs exactly these three Atlas Business skills and practices one with you:
Scroll the table sideways to see every column. With a keyboard, focus the table and use the arrow keys.
| Skill | Use it for |
|---|---|
| company-interview | Explain goals and bottlenecks; review a proposed company brief. Saving needs separate sharing consent. |
| customer-briefing | Prepare for one selected customer or job using cited, bounded records. |
| follow-up-review | Review selected jobs, quotes and invoices; draft a follow-up for you to send. |
The daily operations brief belongs to follow-up-review. Skills are optional and do not gate MCP onboarding. Complete the company and known-customer checks above, confirm the result in Atlas, and repeat a useful task yourself in a fresh chat before treating initial onboarding as complete.
4. Use an optional skill for the next decision
Scroll the table sideways to see every column. With a keyboard, focus the table and use the arrow keys.
| Need | Ask in the named skill's chat |
|---|---|
| Update company context | company-interview: “Interview me about our goals and where work gets stuck. Show the proposed brief before any save.” |
| Prepare for a conversation | customer-briefing: “Brief me on [exact customer or job]. Use a small page of connected records, show source IDs and dates, and separate Jobber from QuickBooks.” |
| Choose follow-ups | follow-up-review: “As of today, review up to five pending Jobber quotes and five overdue QuickBooks invoices. Refresh the one I select and draft a message for me to review. Do not send it.” |
| Start the day | follow-up-review: “Give me a bounded daily operations brief from active sources. Show what was checked, what was missing or partial, and the next records I should review. Do not send or save anything.” |
Review any draft and send it yourself. Atlas's bounded reads cannot prove that there are no other customers, calls, messages, invoices or projects. A possible missed follow-up is a reason to inspect the source, not a verified lost lead.
Optional sources
Your adviser prepares the project, provider app/configuration and exact account bindings. You authorize the business account separately. Keep those healthy connections during the cutover; changing tool names does not require a new provider grant. Gateway setup is separate from a source card's Connected status.
For QuickBooks, Gmail, Outlook, Calendar, Drive, Sheets, Excel, OneDrive, Contacts, Forms or another supported toolkit, Atlas searches the live Composio capabilities, inspects the selected action's argument schema and uses generic execution. Returning schemas does not install more ChatGPT tools. There are no fixed Atlas per-action wrappers. Choose one useful task, a known account/resource and a bounded page/window; check native IDs, currencies, custom fields and partial coverage. Missing access is an evidence gap, not proof there are no records.
Permitted restricted Platform reads use atlas_gateway_read with normal atlas:read; atlas_gateway_read_result retrieves the saved outcome without running the action again. This route excludes scripts, proxy, connection management, other helpers, account overrides, custom tools and follow-up authorization prompts. It has its own session and result history. It cannot retrieve offloaded resources. All other execution needs separate business-change permission and exact approval. Direct consumer execution remains blocked; the consumer-project route is a candidate without live restricted-read acceptance. If the needed route is unavailable, state the evidence gap and continue with Jobber/context. Do not reconnect a healthy source or approve a different action merely to get past a refusal. One successful Gmail policy sample does not prove every action or all former reader behavior.
5. Changes, auto-run and approval
Jobber retains 71 change operations. Ask for one specific change at a time. Eligible low-risk Jobber changes can run automatically only after you, the owner, enable auto-run in Review changes and accept its risk acknowledgement. Other changes, including high-risk ones, need your exact approval on a card in chat. Staff may block provider changes or auto-run.
As the company owner, you can review your own requests and requests made by your company's members. Members cannot approve as the owner. Review the exact saved request and click Approve or Decline on its card. Saying “yes” or asking the model to approve never authorizes execution or enables auto-run. If your chat client cannot display approval cards, use a supported MCP Apps client. The Atlas website keeps history, account settings and auto-run controls; it cannot approve, run, retry or decline a business change.
Non-Jobber work uses generic Composio execution. Review the entire stored request, including any batch, script or connection changes. There is no separate Outlook approval opt-in and no QuickBooks/Gmail auto-run. A completed outer response does not independently verify every nested action or promise a provider readback. Ask for a separate authorized readback when needed.
For Outlook mail, check recipients, subject, body and whether the action drafts or sends. A request to send an existing draft identifies that draft; it does not verify its current mailbox content. Follow-up suggestions remain unsent drafts until you separately request and approve a send.
Cards expire and must be reviewed again when stale. A new card does not change the request or extend an existing approval's deadline. If Jobber offers an explicit retry after a proven refusal, review the saved change and click its retry button; only one such retry is available within the original deadline. Atlas does not retry automatically. If an approval response is lost, check the saved result before taking another action. Keep the original reference for any executing or uncertain request and contact your adviser for reconciliation; never prepare a replacement to obtain a clearer result.
Historical website approvals and retired QuickBooks/Gmail receipts remain records, with reconciliation for uncertain outcomes. They do not authorize new gateway requests or another dispatch. Source retirement does not erase provider data, credentials or the existing connection/revocation/closure duties.
6. Decide what Atlas remembers
Provider reads and provider changes are separate from optional content sharing. Sharing can stay off while you use the three skills. Only the owner can change it in the account. When sharing is enabled, review the exact proposed company brief or feedback before asking Atlas to save it; wait for a receipt and version. Avoid raw messages and unnecessary personal data. Atlas does not automatically receive your whole ChatGPT conversation. Turning sharing off prevents new optional saves; use the account's saved-item controls to delete existing items.
If something stops working
Scroll the table sideways to see every column. With a keyboard, focus the table and use the arrow keys.
| What you see | What to do |
|---|---|
| Atlas keeps opening the wrong workspace after signing out | Select Use a different account on the sign-in page or in your workspace navigation. Sign in with the account agreed with your Atlas adviser. Check the workspace name before connecting a provider. |
| Atlas could not verify the Jobber company during connection | Return to your account and select Connect or Reconnect Jobber to start a new authorization. Reloading the failed page cannot restart that attempt. Contact your adviser if it keeps failing. |
| Invitation sign-in uses the wrong account, or email is not verified | Open the invitation link from your email again and sign in with the invited account. If its email is not verified, verify it first. If you only need your existing workspace, select Sign in. |
| Invitation link has expired or was already used | Ask your Atlas adviser for a fresh link. If you already accepted it, just sign in to your account. |
| Your session expired while you were working | Sign in again. Atlas returns you to the page and explains that the last form was not saved; submit it again. After a Jobber connection, press Connect again. |
| Your setup progress changed | Refresh your workspace and review its current next step. When Atlas asks you to repeat your check, open a fresh ChatGPT conversation, select Atlas, and verify your business and a known customer again. Return to Atlas, refresh, and confirm the result. Use the connection instructions if Atlas is missing or will not connect. |
| Could not create MCP app, or sign-in succeeds then connection fails | Check your account-selected setup route. For URL sign-in, ask Atlas to verify automatic client registration (CIMD), your company's selected client and grant, and the OAuth exchange; there is no shared client secret for you to enter. For the preregistered route, ask Atlas to verify the supplied client ID, registered authentication method, exact callback and token exchange. Confidential post/basic clients need the matching secret; public none clients must leave it empty. If the route is unresolved, your adviser must finish setup first. Never substitute Jobber credentials or reconnect a healthy Jobber account to fix ChatGPT login. |
| Service access required, or your account says the service has ended | Ending service is a pause: ChatGPT cannot read or change your business systems through Atlas, but your connections are kept and you can still sign in. Saved company content is deleted 30 days after service ends unless service resumes first. Check the service status in your account and contact your adviser to resume. An active provider connection may still be healthy. |
| This Atlas account is closed | Atlas access for the company has ended. Atlas has removed, or is still removing, its access to your connected systems; you can also remove it yourself in the connected-apps settings of Jobber, QuickBooks, Google or Microsoft. Contact Atlas support if this is unexpected. Atlas tells you if a provider may still list its access. |
| Atlas staff have turned off changes to a provider | The ban remains binding on its execution paths. Jobber and permitted restricted Platform reads stay separate from provider-write settings. Do not use another helper to bypass the ban. Ask your adviser about the permitted route. |
| QuickBooks setup unfinished | Finish the original authorization page in the same sign-in session, if it is still valid. If the link has expired and your account shows Connect again, select it: Atlas cancels the unfinished attempt first, then starts a new one. If it shows no Connect again button, contact your Atlas adviser before starting another attempt. Returning to the account or an expired link does not by itself cancel provider access. |
| Jobber shows Needs reconnection and a Reconnect Jobber button | Jobber stopped accepting Atlas's saved authorization. Select Reconnect Jobber and sign in to the same Jobber company; you do not need to disconnect first. |
| QuickBooks or an optional source asks you to reconnect | Use your account to reconnect and verify the same company or account. For QuickBooks, select Disconnect first and finish remote cleanup before reconnecting. If Retry disconnect remains visible, complete that step or contact your adviser. |
| Atlas tool unavailable | Start a fresh conversation with Atlas enabled; have your adviser check the MCP connection using your account-selected setup route. Skills are not required for MCP reads. |
| Optional skill unavailable | If you chose to add skills, have your adviser verify the three native skill installations and retry in a fresh conversation. A copied prompt is not an installation check. Deferred skills do not block MCP onboarding. |
| Photos visible in Jobber are missing from Atlas | Atlas reads photos attached to internal notes. Images saved only in a quote's Images section are outside that list. Attach the image to a note on the intended record and ask again. An empty result does not prove there are no images elsewhere in Jobber. ChatGPT may ask for one-time approval to open a returned file. |
| Partial results | Use only the stated page and date coverage, and ask for the next page or a single record when a result says more exists or a long text was shortened. |
| Write outcome unknown | Keep the original change reference; check its receipt and the provider record before any new proposal. |
To remove or reinstall Atlas in ChatGPT, use ChatGPT's plugin or app controls, then follow your account-selected setup route and repeat the useful-read check. This does not disconnect your business providers. Disconnect on an Atlas provider card instead stops that company's Atlas access to the provider for all users and connections, and attempts to revoke provider access. Use it only when you intend that company-wide effect; complete any remote-cleanup warning or contact your adviser.
For a weekly habit, review a few important follow-ups, inspect the original records, and update the company brief only if you choose to share it. Your Atlas account shows saved work and a Find a change or receipt lookup for an existing change ID. Your signed order or account provides support and service terms. Paid access has a finite term; payments are handled directly with Atlas outside this app. There is no Stripe or other payment processor, and disconnecting a provider does not itself end a separate service agreement.