Skip to main content

Connect the Documentation to Your AI Assistant

Matouš Čmelík
FW Developer

The public documentation now has an MCP endpoint, so you can plug it straight into Claude, ChatGPT, Cursor or any other AI assistant. The assistant then searches these pages instead of guessing, and answers with links you can open and verify.

The endpoint

https://docs.silixcon.com/mcp

It is public and free to use — no account, API key or sign-in. It speaks Model Context Protocol, the protocol AI assistants use to talk to external tools.

In Claude it is Settings → Connectors → Add custom connector → paste the URL. Other clients are just as quick, and the full list is in AI assistants (MCP).

What changes for you

Ask about a parameter, a state variable, a shell command, a CAN id or a hardware limit, and the answer comes from the documentation with the URL of the exact section it came from. That last part matters most: you can check the source instead of trusting a summary.

Public site only

Why only docs.silixcon.com?

The endpoint searches only what is published on docs.silixcon.com, and no private instance has a /mcp route of its own.

All private instances (*.private.silixcon.com) intentionally use a different, fully local search engine that does not send any information to third-party servers. Keeping your searches on private instances completely private is the reason this feature exists on the public site only.

Still read the page

The assistant receives matching sections, not the whole documentation. For anything safety related — powering, precharge, protections, current limits — open the linked page before you act on the answer.