How Do I Use OBIE's MCP Server as a Creator?
Connect your AI service to https://mcp.obie.io/mcp and sign in with your OBIE creator or team member credentials. The read-only connection lets you retrieve hub content and user information within your account permissions; it can't save changes to OBIE.
Connect your AI service to https://mcp.obie.io/mcp to ask questions about your OBIE hubs, content, and users. The connection is read-only: your AI can retrieve information and help you analyze it, but it can't edit your hub or save changes back to OBIE.
MCP stands for Model Context Protocol. It's a way for an AI service, such as Claude or ChatGPT, to retrieve information from another service when you ask it a question. You don't need to run your own server.
What you can use it for
Use the creator connection to review your hub's structure, read user answers and generated results, or prepare for a coaching session. It can also retrieve records such as user login information, offers, purchases, and documents where your account permissions allow.
For example, you could ask:
- "Find my Launch Planning hub and summarize its journeys and milestones."
- "Find Jennifer Walsh in my Launch Planning hub. Summarize her answers and generated results for the Audience milestone, and identify three useful coaching questions."
- "List the users in my Launch Planning hub and show their last recorded login. Distinguish missing login data from a confirmed login."
Use your actual hub, person, and milestone names. Ask your AI to identify the records and milestone version it used, and to tell you when data is missing rather than guess.
Before you connect
You'll need your OBIE creator or team member email and password, plus an AI service that supports remote MCP connections with sign-in. Your AI provider's plan and workspace settings determine whether you can add a custom connection.
Read the AI provider's privacy and data controls before connecting. Information retrieved from OBIE is sent to that provider, which may include confidential client information. Only connect if you're authorized to share the information available through your account.
Add the creator connection
- Open your AI service's custom MCP connection setup.
- Name the connection OBIE Creator, or another name you'll recognize.
- Enter https://mcp.obie.io/mcp as the server URL. Use the full address, including /mcp.
- Start the connection's sign-in flow. On the OBIE page, read the Third-Party AI Data Notice and select its acknowledgment if you agree and you're authorized to share the information.
- Enter your OBIE creator or team member email and password, then select Sign in. Enter your password on OBIE's sign-in page, not in an AI chat.
- If OBIE shows Choose an organization, select the account you want this connection to use.
- Return to your AI service and finish its connection setup.
Each creator connection stays within one organization. If you work in more than one, add a separate connection for each and give them distinct names.
In Claude
Open Customize → Connectors → + Add → Add custom connector, name the connection, and enter the creator 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 OBIE connection.
If you're in a managed Claude workspace, your workspace's connector permissions may limit who can add one.
In ChatGPT
On ChatGPT web, open Plugins → + → Add custom MCP server. Name the connection, enter the creator 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 you don't see these controls, 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 the creator server URL, https://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 the OBIE connection, find my [hub name] hub and list its journeys."
Check the result against OBIE. If your AI answers without using the connection, select or enable OBIE in that conversation and ask again.
For a larger report, ask it to retrieve all pages of results before summarizing. A partial list isn't proof that other records don't exist. When reviewing someone's work, specify the journey, milestone, and version so results from different versions aren't mixed together.
Enable MCP for your hub's users
Your creator connection and your users' connections are separate. You don't need to enable user MCP access to use the creator server.
To let users connect to their own work:
- Open Hub Settings → Login → Settings.
- Turn on MCP access.
- Select Save Pending Edits to make the change live. Review any other pending edits before saving.
- Copy the hub-specific MCP URL shown with the setting and share it with your users. It looks like https://yourhub.mcp.obie.io/mcp.
MCP access is off unless you've enabled it for that hub. Turning it on doesn't give anyone new hub access or expose one user's work to another. Users still need their own hub login and access.
To turn user MCP access off, switch off MCP access and select Save Pending Edits. That stops future user access through the hub's MCP connection, including existing user sessions. It doesn't remove information already retrieved by an AI provider.
If something doesn't work
- Sign-in fails: use your creator or team member credentials with the creator URL. A user's hub login belongs on that hub's user MCP URL.
- The wrong account appears: create a separate connection and choose the correct organization during sign-in.
- A record is missing: confirm the account, hub, person, and version. Ask the AI to search by name and finish paging through results. Compare with OBIE before treating the report as complete.
- The AI says it updated OBIE: check OBIE directly. This connection can't make those changes; any rewritten material stays in the AI conversation until you apply it yourself.
Frequently asked questions
- Can my team members connect too?
- Yes. Team members use the same creator server URL and their own OBIE credentials. Their access depends on their account permissions; they shouldn't use your login.
- Can I build or edit a hub from my AI chat?
- Not through this connection. It retrieves information. Your AI can help draft changes, but you'll apply those changes in OBIE.
- Should I give users the creator server URL?
- No. Give them the hub-specific URL shown under Hub Settings → Login → Settings. The creator server is for creators and team members; the hub-specific server is for users accessing their own work.
- Does disconnecting delete information my AI has already retrieved?
- No. Disconnecting doesn't erase information already received by the AI provider. Use that provider's conversation, retention, and deletion controls to manage those copies.
