More and more people ask Claude or ChatGPT which frame or wheelset to buy. The answers are built from whatever the model remembers from the web, which for Chinese direct-to-consumer parts is usually thin and often a year out of date. So the site now has an MCP server: an interface that lets such an assistant query the catalogue directly, with current prices, geometry and the review summaries, instead of guessing.
MCP (Model Context Protocol) is the standard Claude, ChatGPT, Cursor and others use to connect to outside tools. You add the server once, sign in with your MyBike.parts account, and from then on the assistant can look things up here while it answers you.
What an assistant can look up
The server offers the same data the site shows, in a form an agent can work with:
Search across the catalogue (about 1,800 parts and bikes) by text, category, brand, price and weight, plus the spec filters of each category: frame type, tyre clearance, rim depth, freehub and so on. Unlike the category pages, any number of filters can be combined.
Part details: specs, configurations, shop links with current prices, frame geometry per size, and the review summary with its pros, cons, key facts and FAQs. Every point in the summary carries links to the reviews it came from, YouTube videos with the timestamp where the part is discussed, forum threads and Reddit posts.
Similar bikes by geometry: stack, reach, angles, chainstay, wheelbase and the rest, compared size by size. The reference can be a bike that is not sold here, like a Canyon Grail or a Specialized Crux, so "something like my current bike, but cheaper" becomes a question the assistant can actually answer. Over 300 frames and bikes have geometry.
This is what that looks like in Claude. I asked for a relaxed gravel bike along the lines of a Canyon Grizl with room for 50 mm tyres. Claude asks before it uses a tool for the first time:
It then went through the categories and filters, ran the geometry comparison against the Grizl, kept what clears 50 mm and read the review summaries of the candidates:
The scores, prices, clearances and the "quality control is uneven" in that answer all come from the site. The ranking and the wording are Claude's.
Your own builds
If you keep your bikes in the build editor, the assistant can read them too. Asking for my builds lists them, and asking about one gives a summary of all 39 parts:
It can also change a build. In the summary above Claude noticed an 11-speed cassette left over from an older build next to a 12-speed groupset. I asked it to swap that for the Shimano 12-speed cassette I actually use, and it did:
That first attempt also showed a gap: the tools did not know about wheelsets yet, so the new cassette ended up next to the old one in the same wheelset, and Claude's "each wheelset has its own cassette" was a guess. The tools now say which wheelset a part belongs to and which one is in use, and a cassette is swapped within its wheelset, the way the build editor does it.
Three tools do the writing: create a build from a parts list (a spec sheet copied from a shop page works), swap a part in one slot, and remove a part. When a line of the spec sheet matches a part in the catalogue, the build links to it with its price and weight. When it does not match clearly, the part goes in as a custom entry and the assistant is told which catalogue parts it might have meant, so it can ask you. The matching errs on the side of not guessing: "GRX 2x12" does not become the 1x12 groupset we have. Builds created this way are private until you publish them yourself.
Planning a bike from scratch
The build tools are not only for bikes you already own. The more interesting use is putting a new one together in a conversation, with the assistant doing the looking up:
I want to build a gravel bike for bikepacking. Carbon frame with at least 50 mm clearance and mounts on the fork, 1x drivetrain, wheels around 1400 g, everything together under 2500 EUR. Put it in a new build on MyBike.parts.
The assistant searches frames by clearance and price, checks the review summaries for the things that tend to go wrong (paint, headset, bottom bracket), then picks a groupset and wheels that fit, and writes the result into a new build with prices and weights. What it could not find in the catalogue goes in as a custom part, so the list is complete even where the site has gaps. From there it is an ordinary build: you can change it on the site, or keep asking ("swap the wheels for something deeper", "what would the frame weigh in size L") and let the assistant edit it.
The same works in the other direction. Paste the spec sheet of a complete bike from a shop page and ask for a build of it, then ask what the same bike would cost built up from a frameset.
Builds with two wheelsets, say a road and a gravel set, are understood as such: the assistant is told which one is in use and only that one counts towards weight and price, the same as on the build page.
Worth knowing: the assistant decides what "fits". The site gives it the specs, the prices and what reviewers said, but it does not check compatibility itself. Whether that cassette works with that freehub is still something to confirm before ordering.
Suggesting missing parts
When a part is missing, the assistant can suggest it: title, category, shop link, weight, specs, review videos. That does not go live directly. It lands in a queue, I get a mail, check it and publish it or not. The suggestion counts towards your points once it is accepted, the same as adding a part on the site.
How to connect
You need a MyBike.parts account with a confirmed e-mail address.
Claude (claude.ai and the desktop app): Settings, Connectors, "Add custom connector". Give it a
name and the URL https://mybike.parts/mcp. Claude then opens the MyBike.parts login and asks you
to confirm which access it gets.
Claude Code: claude mcp add --transport http mybikeparts https://mybike.parts/mcp, then
/mcp to sign in.
Other clients that support MCP over HTTP work the same way. For tools without a sign-in flow
you can create a personal access token on your profile page and send it as an
Authorization: Bearer header.
Connected apps and your tokens are listed in the same place, each with when it was last used and a button to revoke it:
Everything is also on mybike.parts/mcp-server, including the list of tools.
Worth knowing
Limits. Each account can make 10 tool calls a minute and 300 a day, and a search returns at most 20 results. That is enough for a conversation about a bike; it is not meant for copying the catalogue. The limits are per account and I can raise them, so if you are in the middle of a big build and keep running into them, get in touch and I will lift yours.
The assistant can still be wrong. It gets correct data from here, but what it makes of it is its own, and it fills gaps with plausible guesses, as the cassette example shows. Check the build page before you order anything.
Similar means similar geometry, nothing else. Material, weight and price are separate filters. A bike without geometry data does not show up in that comparison at all.
Prices are the current shop prices the site tracks, in EUR where the shop offers it.
What you can revoke. Connected apps and personal tokens are listed on your profile page and can be revoked there. Changing your password revokes all of them. Tool calls are logged per account, so I can see when something breaks or someone hits the limits.
This is the first version. If your assistant gets stuck on something, or you would like it to be able to do something it cannot, mail me. I read all of it. No account needed to look around the site, but for the MCP server you need one, and you can create one for free.