How Do I Use My OBIE Hub's MCP Server as a User?
Once your hub's creator has enabled MCP access, connect your AI service to the hub-specific URL, such as https://yourhub.mcp.obie.io/mcp, and sign in with your own hub credentials. The read-only connection retrieves your available work in that hub without changing it.
Use your hub's MCP connection to let your AI retrieve your own OBIE answers, generated results, and other available work. The hub's creator must enable MCP access first, and you'll sign in with your own hub email and password.
The connection is read-only. You can use retrieved information in an AI conversation, but it can't save answers, generate results inside OBIE, or mark Steps complete.
What you can use it for
MCP stands for Model Context Protocol. It lets an AI service, such as Claude or ChatGPT, retrieve information from your OBIE hub when you ask.
Your connection can read the hub's available published journeys, milestones, Steps, and questions, plus your own answers, generated outputs, milestone versions, files, conversations, and timelines within that hub. It doesn't give you access to other users' work or the creator's private prompts.
For example, try:
- "Find my answers and generated results for the Audience milestone. Summarize the main decisions I've made."
- "Use my completed work in the Launch Planning journey to draft a one-page action plan."
- "Compare my two versions of the Audience milestone. Tell me which version each finding comes from."
Use the actual names from your hub. Any new plan or rewrite your AI creates stays in that AI service unless you bring it back into OBIE yourself.
Before you connect
You'll need access to the hub, your hub email and password, and an AI service that supports remote MCP connections with sign-in. Your AI provider's plan and workspace settings may affect availability.
You'll also need the hub-specific MCP server URL. It looks like https://yourhub.mcp.obie.io/mcp, with the hub's OBIE slug in place of yourhub.
Use the MCP address supplied for your hub, not its normal website address or a custom domain. The creator's https://mcp.obie.io/mcp address isn't the user connection.
How MCP access is enabled
You can't turn MCP access on from your user account. A creator who manages the hub enables it under Hub Settings → Login → Settings → MCP access, then selects Save Pending Edits.
If you see This AI Hub does not provide MCP access., the hub hasn't enabled it. You can keep using the hub normally without connecting an external AI.
Add your hub's connection
- Open your AI service's custom MCP connection setup.
- Give the connection a name you'll recognize, such as My Launch Planning Hub.
- Enter your hub-specific server URL, including https:// and /mcp.
- Start the connection's sign-in flow. On the hub's OBIE sign-in page, read the Third-Party AI Data Notice. Select the acknowledgment only if you agree and you're authorized to share the information available through the connection.
- Enter the email and password you use as a user of that hub, then select Sign in. Don't put your password in the AI chat.
- Return to your AI service and finish its connection setup.
If you're also an OBIE creator, use your user account for this hub connection. The hub-specific MCP server doesn't accept creator or team member sign-ins as a substitute.
In Claude
Open Customize → Connectors → + Add → Add custom connector, name the connection, and enter your hub's MCP server URL. Select Continue, review the detected authentication settings, and continue with sign-in enabled. Finish with Add and complete the OBIE sign-in flow when prompted.
In a conversation, open + → Connectors and turn on your hub's connection.
Managed workspaces may restrict who can add connectors.
In ChatGPT
On ChatGPT web, open Plugins → + → Add custom MCP server. Name the connection, enter your hub's MCP server URL under Connection, and select OAuth authentication. Review the risk warning, select I understand and want to continue, and select Create as a plugin. Complete OBIE's sign-in flow when prompted.
Install the resulting plugin, then type @ in a conversation and select it.
If those controls aren't available, check your account's custom MCP availability and workspace permissions.
Official setup guides for your AI service
Use your AI provider's guide for its current connection screens and account requirements. Enter your hub-specific MCP URL, such as https://yourhub.mcp.obie.io/mcp, wherever it asks for the MCP server address.
- Claude: Get started with custom connectors using remote MCP. Covers adding a connector, signing in, and enabling it in a conversation, including managed-workspace setup.
- ChatGPT: Connecting custom MCP servers. Covers setup and workspace permissions. The guide lists Business and Enterprise/Edu availability; a workspace administrator may need to add the connection first.
- Grok: Connectors. Follow Custom MCP connectors: open grok.com/connectors → New Connector → Custom, enter the server URL, and complete authentication. Business and Enterprise workspaces require administrator setup first.
- Google Gemini: Connect and manage custom apps. Covers adding a server under Settings → Connected Apps → Custom apps. Google currently requires a personal Google Account, age 18+, US availability, English, and Keep Activity on. Work and school accounts aren't supported for this feature.
Check that it works
Ask: "Using my OBIE connection, list the published journeys available in this hub."
Then ask it to retrieve your work from one named milestone. Compare the answers and generated results with the same milestone version in OBIE.
If your AI doesn't use the connection, select or enable it in that conversation and try again. If something is missing, ask it to search by name and finish retrieving all pages before drawing a conclusion.
Each connection stays within the hub in its URL. If you use another OBIE hub, add a separate connection with that hub's MCP URL.
Keep control of your information
Connecting is optional. Information retrieved through MCP is sent to the AI provider, which handles it under its own terms, privacy policy, account plan, and settings.
Connecting OBIE doesn't change that provider's data controls or automatically opt you out of model training. Review those controls before sharing personal or confidential information.
You can disconnect OBIE in your AI service when you no longer want to use it. Disconnecting doesn't delete information the provider has already received, including copies in conversations. Use that provider's controls to manage or delete those records.
If something doesn't work
- MCP access isn't available: the hub's creator controls whether the hub allows it. You can still work in OBIE without it.
- Sign-in fails: check that you're using this hub's user credentials and its exact MCP URL. If you've never set a password, use the password-setup link in your welcome email or the hub's password-reset flow.
- A journey or Step is missing: confirm that it's available to you in OBIE. Your connection doesn't expose unpublished creator drafts or bypass access restrictions.
- Your work looks different: check the milestone version. Ask the AI to identify the version and source records it used.
- Your AI says it completed a Step: open OBIE to check. Writing something in your AI conversation doesn't complete that Step in OBIE.
Frequently asked questions
- Can the AI read another user's answers?
- No. Your user connection is limited to your own activity in that hub, alongside the published hub content available to you.
- Can I finish a journey entirely from Claude or ChatGPT?
- Not through this read-only connection. Continue answering questions and generating your Step results in OBIE. Your external AI can help you think through and reuse your existing work.
- Do I need a separate connection for every hub?
- Yes. Each user connection is tied to the hub in its server URL, even if you use the same email address in more than one hub.
- Do I need MCP to use OBIE?
- No. It's an optional connection for using your OBIE work in another AI service. You can keep using OBIE directly without it.
