LearnMCP-xAPI

Created By
DavidLMSa year ago
An open-source MCP (Model Context Protocol) server that enables AI agents to record and retrieve learning activities through xAPI-compliant Learning Record Stores
Overview

What is LearnMCP-xAPI?

LearnMCP-xAPI is an open-source Model Context Protocol (MCP) server that allows AI agents to record and retrieve learning activities through xAPI-compliant Learning Record Stores, bridging the gap between AI interactions and learning analytics.

How to use LearnMCP-xAPI?

To use LearnMCP-xAPI, integrate it with your AI tutoring systems or educational analytics platforms. Follow the installation instructions on the GitHub repository to set up the server and connect it to an xAPI-compliant Learning Record Store.

Key features of LearnMCP-xAPI?

  • xAPI 1.0.3 compliance for interoperability with educational technology.
  • Native support for the Model Context Protocol (MCP).
  • Plugin architecture for multiple Learning Record Store integrations.
  • Intelligent statement generation from natural language learning activities.
  • Contextual retrieval of learning histories for personalized AI responses.

Use cases of LearnMCP-xAPI?

  1. Building adaptive AI tutoring systems that adjust based on student progress.
  2. Creating personalized learning assistants that recommend next steps.
  3. Enabling educational analytics platforms to gather evidence of learning.

FAQ from LearnMCP-xAPI?

  • Can LearnMCP-xAPI be used with any Learning Record Store?

Yes, it supports multiple LRS implementations through its plugin architecture.

  • Is LearnMCP-xAPI free to use?

Yes, it is open-source and released under the MIT License.

  • What programming language is LearnMCP-xAPI written in?

LearnMCP-xAPI is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DavidLMS
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago