Geduk LMS

fr.gedukPublished by geduk.frOfficial publisherv0.2.0Updated Oct 24, 2026

Run the Geduk LMS from an AI assistant: courses, sessions, enrolments, users and catalogue.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant work with a Geduk LMS instance: courses, sessions, enrolments, users and catalogue.

What you can do
This remote MCP server connects an AI assistant to the Geduk learning management platform. According to the registry description, it covers courses, sessions, enrolments, users and the catalogue, so an assistant can look up and act on that training data. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Use it when your organisation runs its learning management on Geduk and you want an assistant to help with course, session, enrolment, user or catalogue information inside that platform. It is not useful if you do not have a Geduk account.
Requirements
A remote MCP endpoint at over streamable HTTP. Authentication is required: a bearer access token sent in the Authorization header, issued by your Geduk platform through OAuth 2, with a client registered under Integration > OAuth2 clients. No packages or environment variables are declared.
Before you install
The server requires a bearer access token in the Authorization header; treat it as a secret and do not share it. The manifest states that actions run with the connected user's own rights, so anything the assistant does affects real LMS data under your permissions. The manifest does not list the tools, so review what the assistant can change before granting access.

Installation

In SourceWeft

  1. Open Geduk LMS in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/fr.geduk%2Flms/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "geduk-lms": {
      "type": "http",
      "url": "https://app.geduk.fr/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.2.0LatestOct 15, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.