MYOPL integrations
Build with MYOPL
Start with public pickleball knowledge. Contact MYOPL to discuss personal account or server access; credentials are not issued automatically from this page.
Public MCP
Send MCP JSON-RPC requests with HTTP POST. Use initialize, tools/list and tools/call. No API key or HMAC credentials are required.
- search_pickleball_rules: Search the official pickleball rulebook.
- search_myopl_help: Search product help.
- search_myopl_website: Search public MYOPL website information.
- get_public_player_rating: Look up published ratings by exact username.
Request a personal integration
Use the contact form and select General questions and partnerships. Include your application name, company website, use case, exact HTTPS OAuth callback URLs and requested permissions. Do not include passwords or secrets.
Personal OAuth connections are not available yet. MYOPL will review integrations before registering and enabling their public OAuth clients. When available, users will approve access with authorization-code OAuth and S256 PKCE. Self-service client registration is not available.
- 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 confirmation on MYOPL.
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. Contact MYOPL about provisioning, rotation and access requirements.