
Ferrolaser Parts
io.github.jinweihan-aiPublished by GitHub account jinweihan-aiv1.0.0Updated Oct 24, 2026
Fiber laser parts knowledge: laser sources, cutting/welding heads, CNC controls, alarm codes.
Overview
Hosted knowledge base of fiber laser machine parts — laser sources, cutting and welding heads, CNC controls and alarm codes — searchable by an AI assistant.
- What you can do
- Search 521 structured knowledge cards by keyword and brand, with brand-alias expansion
- Open a full card for specifications, wiring, alarm/error codes and consumable part numbers
- List covered brands with card counts and short intros
- Read category overviews such as anatomy, laser sources, cutting heads, welding heads and control systems
- Send a sourcing or quote inquiry to the vendor's sales engineers
- When to use it
- Useful when an assistant has to answer practical questions about fiber laser equipment: what an alarm code means, which cutting head fits a given source power, how a control system is wired, or which consumable part numbers apply.
- Requirements
- A remote Streamable HTTP endpoint; no authentication, environment variables or headers are needed for the knowledge tools. Card bodies are in Chinese, so the client translates them. Self-hosting is possible via Docker with an optional GATEWAY_TOKEN for inquiry routing.
Installation
In SourceWeft
- Open Ferrolaser Parts in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.jinweihan-ai%2Fferrolaser-parts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ferrolaser-parts": {
"type": "http",
"url": "https://mcp.ferrolaser.com/mcp"
}
}
}README
FerroLaser Parts Knowledge MCP Server
Fiber laser machine parts & components knowledge base as an MCP server — 521 structured knowledge cards covering fiber laser sources (Raycus, Max Photonics, JPT), laser cutting heads and welding heads (Raytools / Empower, OSPRI, Super Laser), CNC control systems (BOCHU / Friendess FSCUT, CypCut / HypCut): key specifications, wiring diagrams, alarm / error code explanations, consumable part numbers, and selection advice — all distilled from official manufacturer manuals.
Maintained by FerroLaser — an industrial fiber laser machine manufacturer in Jinan, China (laser cutting machines, welding machines, cleaning machines, marking machines, sold factory-direct worldwide).
What can an AI assistant do with this?
- "What does Raycus alarm code XX mean and how do I fix it?"
- "BLT421 vs BM111 cutting head — which fits a 6kW source?"
- "FSCUT2000 wiring: which terminal takes the servo alarm input?"
- "What consumable part numbers does the Raytools BW06K welding head use?"
- "How is a fiber laser cutting machine put together?" (component anatomy overview)
- Send a sourcing / quote inquiry straight to FerroLaser's engineers (
submit_inquiry)
Endpoint (hosted, free)
Transport: Streamable HTTP (stateless). No authentication required for knowledge tools.
Claude Desktop / Claude Code
or in claude_desktop_config.json / .mcp.json:
Cursor / other MCP clients
Add a remote MCP server with URL https://mcp.ferrolaser.com/mcp (Streamable HTTP).
Tools
Card bodies are written in Chinese (distilled from bilingual official manuals) — AI clients translate on the fly; model numbers, part numbers and alarm codes are language-neutral.
Self-hosting
Set GATEWAY_TOKEN env only if you wire submit_inquiry to your own backend; knowledge
tools work without any configuration.
Data & license
- Knowledge cards are distilled from publicly available official manufacturer manuals; no pricing, no BOMs, no customer data. Source PDFs are downloadable at ferrolaser.com/resources.
- Code: MIT. Knowledge data (
app/parts_kb.json,app/overviews/): CC BY 4.0 — attribution "FerroLaser (ferrolaser.com)".
Fiber laser cutting machine · laser welding machine · laser cleaning machine · laser marking machine — FerroLaser, Jinan, China.
Source: README.md at commit 0a35e01
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts