NVMUNDEVELOPERS

The NVMUN developer platform

Your conference.
Your tools.

Connect apps and AI tools to NVMUN with REST APIs and MCP. Register an OAuth client or create an API key using your own conference account.

Registrations & participant services

My Account

Build with registration, school roster, committee assignment, position paper and fee-status tools. Your account's live role sets the limits.

Open My Account console

API & MCP guide

Committee operations

ChairNVMUN

Connect tools to committee workspaces and the actions your Chair role allows. Chair has its own sign-in and permissions.

Open Chair console

Chair API & MCP guide

Two ways to connect

REST: create an API key in a console. The complete key is shown once. Keep it in a secret store and send it only as a Bearer token to its issuing service.

MCP: register a public OAuth client, use authorization-code flow with S256 PKCE, and ask the account holder to approve access. No client secret is issued. Each callback address must match exactly.

Connections stay active until revoked, without an hourly reconnect. Account disablement, role changes or security changes can end access. Read-only is the default; sensitive actions still need exact browser approval.

Endpoints & resources

My Account

REST  https://my.nvmun.org/api/v1
MCP   https://my.nvmun.org/api/mcp

OAuth discovery · Supported actions & gaps

ChairNVMUN

REST  https://chair.nvmun.org/api/v1
MCP   https://chair.nvmun.org/api/mcp

OAuth discovery · Permissions & limits

Card details, payment authorization and credential secrets stay out of the API. Conference roster-release and timetable controls are not exposed.