Canvas Lms MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

          PUB_VER=$(curl -fsSL -H "Authorization: Bearer ${{ secrets.GITHUB_TOKEN }}" https://api.github.com/repos/modelcontextprotocol/registry/releases/latest | jq -r '.tag_name')

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add canvas-lms-mcp -- npx -y canvas-lms-mcp

{
  "mcpServers": {
    "canvas-lms-mcp": {
      "args": [
        "-y",
        "canvas-lms-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.canvas-lms-mcp]
command = "npx"
args = ["-y", "canvas-lms-mcp"]

{
  "mcpServers": {
    "canvas-lms-mcp": {
      "args": [
        "-y",
        "canvas-lms-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "canvas-lms-mcp": {
      "args": [
        "-y",
        "canvas-lms-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CANVAS_API_TOKEN (Canvas personal access token (Account → Settings → Approved Integrations → New Access Token)), CANVAS_BASE_URL (Canvas instance base URL, origin only with no path, e.g. https://school.instructure.com). The author declared them in the registry entry; get the values from the project itself.