LearnMCP MCP Server

An open-source MCP (Model Context Protocol) server that enables AI agents to record and retrieve learning activities through xAPI-compliant Learning Record Stores. The learnmcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

What it actually does

• xAPI 1.0.3 Compliance — Full compatibility with the xAPI specification ensures interoperability with existing educational technology ecosystems,
• MCP Integration — Native support for the Model Context Protocol enables seamless AI agent connectivity
• Plugin Architecture — Extensible plugin system supporting multiple Learning Record Stores with easy configuration switching
• Multiple LRS Support — Built-in support for LRS SQL and Ralph LRS, with architecture designed for easy addition of new LRS implementations
• Flexible Authentication — Support for various authentication methods including Basic Auth and OIDC (OpenID Connect) depending on LRS requirements
• Privacy by Design — Student identifiers are configurable and separate from personal information, ensuring educational data privacy

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — Before starting, ensure you have: - Python 3.8 or higher - Access to an xAPI-compliant Learning Record Store (we recommend [LRS
• Installation — The Installation tool exposed by this server
• Configuration — LearnMCP-xAPI uses a flexible configuration system supporting both environment variables and configuration files

Configuration

You will need 5 environment variables: LRSQL_KEY, LRSQL_SECRET, RALPH_OIDC_TOKEN_URL, RALPH_OIDC_CLIENT_ID, RALPH_OIDC_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before starting, ensure you have: - Python 3.8 or higher - Access to an xAPI-compliant Learning Record Store (we recommend LRS SQL for development) - An MCP-compatible client (such as Claude Desktop)

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. LearnMCP's toolset — Prerequisites, Installation, Configuration — is a fair guide to whether it matches your workflow. It is maintained by DavidLMS; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against LearnMCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the learnmcp mcp server does with a few real requests.