Claude Code runs local processes and can also reach a remote server directly, so it supports every Moodle and Ed Discussion Model Context Protocol (MCP) surface described in MCP servers. Official reference: Connect Claude Code to tools via MCP, fetched 2026-09-21.

Prerequisites

  • moodle-cli and edstem-cli installed and signed in. See Install and Install.
  • Claude Code installed and signed in.

Preferred: moodle mcp connect

This writes a bridge entry to ~/.claude.json at user scope:
The bridge keeps your MCP access token in the OS keychain instead of in this file. Restart Claude Code (or start a new session) to pick up the change.

Manual: project scope

To share the server with a team through source control instead, add a project-scoped .mcp.json at your repository root:

Manual: remote, header auth

Clients that support custom headers can skip the bridge and connect to the Worker directly:
Get <your-token> with moodle mcp connect claude-code --mode remote --show-token, or use moodle mcp pair instead if you’d rather use OAuth — see claude mcp login <name>.

Verify the connection

Each server shows a status: ✔ Connected, ! Needs authentication, or ✘ Failed to connect. Inside a session, run /mcp for the same list plus each server’s available tools, and to complete an OAuth sign-in if one is pending.