Connect an AI assistant to MYOPL with OAuth

Published October 8, 2026

OAuth lets you give an AI assistant permission to use specific MYOPL account features. You sign in with MYOPL and review the requested permissions before allowing access. You do not give the assistant your MYOPL password.

Note

Private MCP access is currently a controlled Admin pilot. Your account must be eligible, the required OPL Intelligence features must be enabled, and the assistant must be registered to connect. Seeing a connection URL does not by itself enable access.

Start the connection in your AI assistant

Open the assistant's connector or integration settings. The assistant must support remote MCP connections with OAuth.
When it asks for MYOPL's private MCP address, use https://api.myopl.net/mcp/personal.
Start the connection. The assistant opens MYOPL's authorization page with the details needed for your request.

The public MYOPL MCP provides public information. Connecting it does not authorize access to your personal account. You do not need the developer portal or a developer API key for this personal OAuth flow.

Sign in and check the account

The authorization page identifies the assistant requesting access. If your existing Messenger sign-in can be reused in the same browser, MYOPL takes you to the permission screen. Otherwise, sign in using the available email/username or SMS option.

On the permission screen, check that the account shown is yours and that you recognize the assistant. Cancel if either is wrong. Never paste your password or an authorization callback into an AI conversation.

Review the requested permissions

Depending on the assistant and your account's enabled features, the request can include:

OPL ratings: read your published OPL ratings.
Sessions: find your league sessions.
RSVP preparation: prepare an RSVP for you to confirm in MYOPL.
Personal statistics: view your own statistics cards. Personal statistics are available to all MYOPL users without a subscription upgrade.

Viewing other players' statistics requires a MYOPL Plus or Elite subscription. This OAuth permission covers only your own statistics.

The screen lists the permissions for that particular request. Allowing RSVP preparation does not submit an RSVP: you still confirm the proposed action in MYOPL.

Allow or cancel

Choose Allow only when you trust the assistant and agree to the listed permissions. MYOPL returns the authorization result to the assistant so it can finish connecting. Wait for that handoff; close the window only when completion is confirmed or the page tells you to do so.

Choose Cancel to deny the request. The page shows that permission was denied and sends the cancellation result back to the assistant. No new connection is approved by cancelling.

Remove access

Use MYOPL's connected-agent page to review your connections and disconnect an assistant. You may need to sign in first. If a connection expires or you remove access, start a new connection from the assistant when you want to use it again.

Why am I seeing “MYOPL OAuth Proxy” and a help link?

This screen can appear when an authorization link is incomplete, invalid, expired, or points to an unknown OAuth page. Opening an authorization address directly, without the assistant's request details, cannot start a connection.

Return to the assistant's connector settings and start again to get a fresh authorization link. Do not edit the URL parameters yourself. If the same screen returns, ask whether that assistant is supported in the current MYOPL pilot, or contact MYOPL support. Include the assistant's name and the visible error, but do not send passwords, access tokens, or callback URLs.

For account controls, see Manage OPL Intelligence Settings. You can also review MYOPL's Privacy Policy and AI Terms.