Skip to content

Connect MCP clients

All clients should point to the remote endpoint:

https://api.wodira.app/mcp

When the client supports OAuth, let it discover WODira metadata and complete login in the browser. The minimum required scope is profile.

The only stable public deeplink we can offer today is Claude’s custom connector flow. It opens the custom connector modal with name and URL prefilled:

For Codex, Cursor, Gemini CLI, ChatGPT, Perplexity, and Grok, use the configurations below. If those clients publish an official deeplink with equivalent behavior, we will add a button here.

Codex supports Streamable HTTP MCP servers in config.toml.

[mcp_servers.wodira]
url = "https://api.wodira.app/mcp"

Then sign in:

Terminal window
codex mcp login wodira

Inside Codex, use /mcp to check that the server is connected and that the hello tool is available.

If you use Claude web, open the direct modal:

If you use Claude Code, add the remote HTTP server:

Terminal window
claude mcp add --transport http wodira https://api.wodira.app/mcp

In a Claude Code session, open:

/mcp

From there you can check status, authenticate, and inspect discovered tools. If your version uses JSON, streamable-http is equivalent to remote HTTP.

Cursor lets you add MCP servers from its MCP settings. Add a remote server named wodira with this URL:

https://api.wodira.app/mcp

If your version lets you edit MCP-compatible JSON, use this block as a base:

{
"mcpServers": {
"wodira": {
"url": "https://api.wodira.app/mcp"
}
}
}

Select Streamable HTTP if the UI asks you to choose a transport. If the client requests authorization, complete the WODira OAuth flow.

Gemini CLI uses settings.json and distinguishes SSE (url) from Streamable HTTP (httpUrl). Use httpUrl for WODira:

{
"mcpServers": {
"wodira": {
"httpUrl": "https://api.wodira.app/mcp"
}
}
}

Then run /mcp in Gemini CLI to check connection, tools, and resources.

For ChatGPT, the recommended path is an app built with Apps SDK/MCP Apps. WODira already exposes tools and UI resources with ui://wodira/... URIs, so a compatible app or connector can use the remote server:

https://api.wodira.app/mcp

In your app manifest/configuration, declare the remote MCP server and enable OAuth for users. Then test hello and a read-only tool before enabling write actions.

Perplexity and Grok frequently change their external connector support. If your plan or workspace offers remote MCP with OAuth, use:

https://api.wodira.app/mcp

If you do not see a remote MCP/Streamable HTTP option, use a currently supported client such as Codex, Claude Code, Cursor, or Gemini CLI. Do not use proxies that paste tokens into prompts unless they are controlled by your team and reviewed for security.

Only for older clients without Streamable HTTP:

https://api.wodira.app/mcp/sse

The associated messages endpoint is:

https://api.wodira.app/mcp/messages

Prefer Streamable HTTP whenever the client supports it.

  1. Connect the wodira server.
  2. Complete OAuth if the client asks for it.
  3. Run hello.
  4. Run a read-only tool such as search_events.
  5. For organizer flows, run organizer_list_my_organizations before operating on events.