Brightspace
Connect Brightspace (D2L) courses, assignments, and org data into agent workflows for edtech products and internal teaching ops.
Overview
Brightspace MCP is a Build-phase MCP server that connects D2L Brightspace to coding agents with 26+ tools, resources, prompts, and a dashboard.
What is this MCP server?
- 26+ MCP tools for Brightspace / D2L operations
- Multi-auth support with YAML config (BRIGHTSPACE_CONFIG, default ~/.brightspace-mcp/config.yaml)
- MCP Resources, Prompts, and a web dashboard bundled with the server
- Stdio npm package brightspace-mcp v1.1.1
- Course and org automation surface for agent-driven edtech workflows
- 26+ MCP tools documented in server description
- npm package brightspace-mcp version 1.1.1
- Environment variable BRIGHTSPACE_CONFIG for config.yaml path
What problem does it solve?
Building or automating around Brightspace means fragile scripts or manual LMS clicks unless agents have a governed API bridge.
Who is it for?
Solo builders shipping edtech side projects, course ops tools, or internal Brightspace automations on top of D2L.
Skip if: Builders with no Brightspace tenant or teams that only need generic PDF or video course hosting outside D2L.
What do I get? / Deliverables
After configuration, agents can call Brightspace-aligned MCP tools and resources instead of one-off HTTP hacks or copy-paste admin work.
- Agent-callable Brightspace tool surface (26+ tools)
- MCP resources and prompts for repeatable LMS tasks
- Web dashboard for monitoring or operating the MCP deployment
Recommended MCP Servers
Journey fit
LMS API wiring is classic Build work when you are integrating a third-party platform into something you ship, even if you later use it in Grow or Operate. Integrations is the right shelf for a multi-tool Brightspace MCP that wraps external SaaS APIs rather than generating UI or running tests.
How it compares
LMS-specific MCP integration, not a general learning-platform skill or static course generator.
Common Questions / FAQ
Who is Brightspace MCP for?
Developers and operators who already use D2L Brightspace and want agent-accessible course and org workflows.
When should I use Brightspace MCP?
Use it in Build when you are integrating Brightspace data or actions into an app, bot, or internal automation you plan to ship.
How do I add Brightspace MCP to my agent?
Install brightspace-mcp from npm, set BRIGHTSPACE_CONFIG to your config.yaml (or use the default under ~/.brightspace-mcp/), add the stdio server to your MCP client, and authenticate per your Brightspace setup.