Configure the MCP server
Point the Oratora MCP server at your account.
The Claude Code plugin configures the Oratora MCP server
(@oratora/mcp) for you automatically — most people never need to touch this page. It's
here for running the server standalone, with another MCP client, or against a
non-production API.
The MCP server is a thin, typed wrapper over the public REST API at
{ORATORA_API_URL}/api/v1, authenticated with a per-account
API key.
Environment variables
| Var | Required | Default | Purpose |
|---|---|---|---|
ORATORA_API_KEY | yes | — | API key from your Oratora account, minted in Dashboard → Developer. |
ORATORA_API_URL | no | https://app.oratora.live | Base URL the server talks to. Override to target a dev/staging deployment. |
Run it
Set your key in the environment the server runs in, then start it with npx:
ORATORA_API_KEY=... npx -y @oratora/mcpTo target a non-production host, also set ORATORA_API_URL (it defaults to
https://app.oratora.live):
export ORATORA_API_KEY="or_live_xxxxxxxx"
export ORATORA_API_URL="https://app.oratora.live" # override for dev/testing
npx -y @oratora/mcpIf ORATORA_API_KEY is missing, every tool call fails with a reminder to create a key
in Dashboard → Developer and run /oratora:setup.
How the Claude Code plugin runs it
The plugin's own MCP config runs the same package for you via npx -y @oratora/mcp, so
once you've exported ORATORA_API_KEY and run /oratora:setup (see
Install the plugin) there's nothing extra to configure.
Developing against the source
If you're working on the server itself:
pnpm install
pnpm build # tsc -> dist/
pnpm start # node dist/index.js