WODira MCP

WODira MCP lets clients such as Codex, Claude Code, Cursor, Gemini CLI, and ChatGPT apps query and operate on events, boxes, bookings, tickets, and organizer tools using the Model Context Protocol.

Canonical endpoint:

https://api.wodira.app/mcp

Use this endpoint when the client supports remote MCP over Streamable HTTP. The SSE transport exists for legacy compatibility, but it is not recommended for new integrations.

Discovery and OAuth

WODira publishes OAuth 2.1 metadata so clients do not need to assume internal endpoints:

Resource	URL
Protected resource metadata	`https://api.wodira.app/.well-known/oauth-protected-resource/mcp`
Authorization server metadata	`https://api.wodira.app/.well-known/oauth-authorization-server`
OpenID configuration	`https://api.wodira.app/.well-known/openid-configuration`

The expected access token resource/audience is:

https://api.wodira.app/mcp

Minimum required scope:

profile

Compatible clients should use discovery and open WODira login/consent during the OAuth flow. A valid Better Auth browser session is also accepted when the client starts the connection from an authenticated browser.

Transports

Transport	Endpoint	Status	Recommended use
Streamable HTTP	`https://api.wodira.app/mcp`	Active	Modern remote clients with OAuth
SSE	`https://api.wodira.app/mcp/sse` + `/mcp/messages`	Legacy	Only if your client lacks HTTP support

The initial connection creates an MCP session. Subsequent calls use the mcp-session-id header managed by the MCP client.

First test

Once the client is connected, run the tool:

hello

Expected response:

Hello from WODira MCP

If hello works, transport, authentication, and basic tool discovery are working.

What you can do

The server exposes tools for three profiles:

Profile	Capabilities
Public	Search published events and get event links
Athlete	View boxes, today’s classes, bookings, tickets, bookmarks, and calendar data
Organizer	List organizations, create events, check metrics, manage orders and tickets

For organizer flows, start with organizer_list_my_organizations and use the returned organizationId in tools that accept it.

Best practices

Connect to https://api.wodira.app/mcp unless you are in a controlled local environment.
Use the MCP client’s OAuth flow when available.
Review tools before allowing write actions such as creating events, refunding orders, or deleting registrations.
Do not paste access tokens into prompts, issues, repositories, or public documentation.
Use hello as a smoke test, then choose tools by intent rather than by name.