Integration

CoderPad integration

CoderPad Interview API: create and manage live coding interview pads and the question bank. Create, list, update, end or delete pads, read a pad's code, environments, events and (on Insights & Analytics plans) transcript, highlights and outline, manage questions and their language variants, and read the organization, its users, pad usage stats and the pad quota. Creating a pad counts towards the pad quota of the billing cycle. Pad join, playback, history and drawing links, AI review reports and the single sign-on URL are not returned; the Screen (assessment) API is a separate integration. Authentication is the API key from the CoderPad settings page sent as a Bearer token.

Connect CoderPad How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in CoderPad.Built from the 23 CoderPad tools below, on the connection you add once.

What you can do with CoderPad

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Question, 6 operations

create_questionCreate questionPOSTCreates a question in your question bank: starter code in contents for a single-file language, or a project template slug in language with file_contents.
delete_questionDelete questionDELETEDeletes a question from the question bank for real.
get_questionGet questionGETReturns one question bank question: instructions, starter code, solution, test cases, files and variants.
list_organization_questionsList organization questionsGETLists the published questions of your organization that are visible to you.
list_questionsList questionsGETLists the published questions visible to you.
update_questionUpdate questionPUTUpdates a question: only the fields sent change. For a project template question, file_contents replaces all of its files.

Pad, 5 operations

create_padCreate padPOSTCreates an interview pad owned by you, for real: it counts towards the pad quota of the billing cycle. Fields left out use the account defaults. Returns the pad and its id.
get_padGet padGETReturns a pad: title, state, language, code, participants and notes; for ended pads on Insights & Analytics plans, the owner also gets transcript, highlights and outline.
list_organization_padsList organization padsGETLists the pads of every user of the organization. Organization owners only, unless the organization opens the pad index to everyone. Page with page.
list_padsList padsGETLists the pads visible to you, newest first. For more pages pass the cursor found in next_page (preferred) or a page number.
update_padUpdate padPUTUpdates a pad: only the fields sent change. Set ended to end the interview, or deleted to delete the pad for real. Owners update their pads; organization owners any pad.

Variant, 5 operations

create_question_variantCreate question variantPOSTAdds a language or project template variant to a question.
delete_question_variantDelete question variantDELETEDeletes a language or project template variant of a question for real.
get_question_variantGet question variantGETReturns one variant of a question with its starter code or files and solution.
list_question_variantsList question variantsGETReturns every variant of the question in a single response. Unlike the other list endpoints, this one is not paginated and has no `total` count or `next_page` / `prev_page` URLs.
update_question_variantUpdate question variantPUTUpdates a variant. Only the fields you send are changed, with one exception: changing `language` to a different language or project template clears the variant's starter files.

User, 2 operations

get_current_userGet current userGETReturns the user the API key belongs to: name and whether they may create pads.
list_organization_usersList organization usersGETLists the users of your organization with their teams. Filter by email to find one user.

Event, 1 operation

list_pad_eventsList pad eventsGETLists the events of a pad, such as participants joining or leaving, code runs and questions being added.

Organization, 1 operation

get_organizationGet organizationGETReturns your organization, its child organizations, teams and users.

Pad environment, 1 operation

get_pad_environmentGet pad environmentGETReturns a pad environment and the current contents of its files. The IDs of a pad's environments are listed in its `pad_environment_ids`.

Quota, 1 operation

get_quotaGet quotaGETReturns your pad usage for the current billing cycle. For organization accounts, this is the organization's quota.

Stats, 1 operation

get_organization_statsGet organization statsGETReturns the number of pads created by each user of your organization over a period of time. Defaults to the last 7 days.

Use CoderPad from Claude Code, Cursor or Codex

Connect CoderPad in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its CoderPad operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect CoderPad

Create your workspace
Sign up free. Nothing to install.
Connect CoderPad once
Add your CoderPad connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.