twbs / twbs/bootstrap

Add MCP server for Bootstrap docs and component API

Open
#42,330 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
MDX
Stars
175k
Forks
78.6k
Avg merge
7h 19m
Merged PRs (30d)
35

Description

Prerequisites
Proposal

An MCP server for Bootstrap could expose structured access to:

Component definitions
props/options
variants and states
accessibility notes
Usage examples
Utility classes
JavaScript behavior APIs
Versioned documentation access
Migration guidance between versions
Links to source SCSS/JS implementation where relevant

Motivation and context

Normally Ai agents are fairly good at getting context for bootstrap, but it could be outdated information the agents suck in or not structured in the best way for agents. In the case where I thought this would be useful recently: I wanted a complete list of all the classes that actually exist, to better scrub through my application on usages where any class doesn't actually exist or have an effect, to remove the excess. A painfully slow and tedious human task with no real benefit, but something an Ai would complete in only a few minutes as long as it was trust-able. This example is mostly useless for practical benefit, because non-existing classes doesn't really matter. On a more realistic example, it's as simple as just the agent being able to write bootstrap better.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing Bootstrap's existing documentation, component definitions, utility classes, and JavaScript behavior APIs to determine what structured data is available. Done means an MCP server exposes the proposed documentation, versioning, migration, accessibility, usage, and source links in a trustworthy form.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, html, javascript, scss
Domain
documentation, tooling, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.