Brightspace

Please install the `brightspace` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js 20 or newer** — Node.js version 20 or higher is required to run the server via npx.
- **Run initial Brightspace setup** — Use the interactive setup wizard to create the Brightspace MCP config file and choose an authentication strategy. For non-interactive environments, use the init command instead. Run: `npx brightspace-mcp@latest setup`
- **Provide Brightspace credentials or token based on auth strategy** — You must configure one supported authentication method in the Brightspace config file created by setup/init. Common options include an API token, username/password, session cookie, or browser-based login.
- **Set required environment variables for your chosen auth strategy** — Depending on authentication method, export the needed secrets such as BRIGHTSPACE_API_TOKEN, BRIGHTSPACE_USERNAME, BRIGHTSPACE_PASSWORD, BRIGHTSPACE_TOTP_SECRET, or BRIGHTSPACE_COOKIE before starting the server, unless your config references keychain or encrypted file storage instead of env vars.

Optional prerequisites:
- Install Playwright and Chromium for browser auth — Required only if using the browser authentication strategy for SSO or JavaScript-heavy login flows. Run: `npm install playwright && npx playwright install chromium`
- Install and run Redis plus ioredis for Redis-backed cache — Required only if your Brightspace config sets session.cache_backend to redis or uses the optional redis section for persistent caching. Run: `npm install ioredis`

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["--yes","brightspace-mcp@latest","serve"]
- optional environment variables:
  - `BRIGHTSPACE_CONFIG`: Path to the Brightspace MCP config.yaml file created by setup/init. If omitted, the default location is typically used. (example: `<path-to-config.yaml>`)
  - `BRIGHTSPACE_API_TOKEN`: Brightspace Valence API token when using the api_token auth strategy and token_ref points to env:BRIGHTSPACE_API_TOKEN. (example: `<your-brightspace-api-token>`)
  - `BRIGHTSPACE_USERNAME`: Brightspace username when using headless or browser auth and username_ref points to env:BRIGHTSPACE_USERNAME. (example: `<your-brightspace-username>`)
  - `BRIGHTSPACE_PASSWORD`: Brightspace password when using headless or browser auth and password_ref points to env:BRIGHTSPACE_PASSWORD. (example: `<your-brightspace-password>`)
  - `BRIGHTSPACE_TOTP_SECRET`: Base32 TOTP secret when using MFA strategy totp and secret_ref points to env:BRIGHTSPACE_TOTP_SECRET. (example: `<your-totp-secret>`)
  - `BRIGHTSPACE_COOKIE`: Session cookie string when using the session_cookie auth strategy and cookie_ref points to env:BRIGHTSPACE_COOKIE. (example: `<your-brightspace-cookie>`)

Note: The MCP server uses stdio transport (`serve`). Authentication details such as base_url, auth strategy, MFA settings, output preferences, writes settings, and optional Redis configuration are stored in the Brightspace config file generated by `setup` or `init`, not in the MCP client config. To enable write tools, start with `npx --yes brightspace-mcp@latest serve --enable-writes` and also set `writes.enabled: true` in the Brightspace config file.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.