MYOPL integrations
Build with MYOPL
Build an integration with MYOPL using the public or personal MCP endpoint below. Find protocol documentation, OAuth permissions and machine-readable API contracts here. For step-by-step setup in your AI app, use Connect your AI.
Published Updated
Public MCP
Use stateless MCP Streamable HTTP with JSON-RPC over HTTP POST. Start with initialize, then tools/list and tools/call. Public access requires no MYOPL account, API key or OAuth sign-in.
- prepare_pickleball_browse: Find public courts, clubs, open play sessions or leaderboard destinations for a named location; no live availability or booking.
- search_pickleball_rules: Search official 2026 USA Pickleball rule excerpts with citations.
- search_myopl_help: Search product help.
- search_myopl_website: Search public MYOPL website information.
- get_public_player_rating: Look up exact four-decimal ratings, Reliability Score, games played/won/lost and points won/lost by username. Compatible clients can display one MYOPL rating card.
Personal MCP (OAuth)
Connect a consenting user’s MYOPL account through OAuth authorization code with S256 PKCE. Personal connections are available with MYOPL Plus and higher plans.
Discover the protected resource and authorization server, then use a supported published client identity or dynamic client registration. Users sign in on MYOPL and approve the requested permissions; they should not need to enter a developer client ID or secret.
Request only the scopes your integration needs. Use the refresh-token grant when access expires, store replacement refresh tokens securely, and retry after temporary rate limits. Users can disconnect access in Messenger under Settings > OPL Intelligence.
| OAuth scope | Permission |
|---|---|
| myopl:rating:read | Read the user’s published OPL ratings. |
| myopl:sessions:read | Find the user’s league sessions. |
| myopl:rsvp:write | Prepare an RSVP for explicit confirmation in MYOPL. |
| myopl:statistics:read | Read the user’s own statistics cards; no package upgrade is required. |
Implement your MCP client
Use MYOPL as a source of structured pickleball data in your assistant or application. Build against the published tool schemas and returned records so you can present MYOPL information in your own interface.
- Negotiate the protocol: Call initialize, then send the negotiated MCP-Protocol-Version header. POST JSON-RPC with Content-Type: application/json and Accept: application/json, text/event-stream.
- Discover before calling: Read tools/list and validate arguments against each inputSchema. Use tools/call with the exact tool name; read structuredContent for application data and content for the text fallback.
- Render one card: Clients that support MCP Apps can use resources/list and resources/read with the rating tool’s UI metadata. Other clients should show the returned ratings and totals as text. Preserve exact rating values, distinguish null from zero, and include MYOPL source links.
- Handle failures by type: Read JSON-RPC errors and tool isError results. Honor Retry-After on HTTP 429. For personal access, handle expired access tokens through OAuth renewal instead of repeatedly sending the user through sign-in.
- Verify the complete flow: Test current data retrieval, the card or text fallback, sign-in, token renewal and user-initiated disconnect in each client you support. A successful tool response alone does not verify every client’s rendering or renewal behavior.
Server integrations and HMAC
Server access is reviewed separately. Approved integrations receive a client identifier and a shared signing secret through a secure onboarding process. HMAC signs requests so MYOPL can verify the sender and request integrity.
Keep signing secrets on your server. They do not belong in browser code, mobile apps or player connection screens. For provisioning, rotation or a new integration, choose AI, API and Developers on the contact form. Include your application name, use case, exact HTTPS OAuth callbacks and requested permissions; do not send secrets.