Developer Tools
bergsonne.io
Provides search and retrieval of Bergsonne hardware tiles, tile drivers, SDK symbols, and documentation.
ENDPOINT 1
https://bergsonne.io/mcp
MCP server metadata
- Name
- bergsonne-knowledge
- Version
- 1.0.0
Bergsonne Labs — Composable, millimeter-scale Tiles — embedded intelligence for physical AI. Fully-encapsulated modules, plus the Studio IDE that composes them. Read-only reference for the Bergsonne tile platform: the tile catalog, per-tile driver APIs, the SDK, and the I²C / pad lookup tables. Tiles are identified as `Family.Name` (e.g. `Sense.TOF`), optionally `Family.Name@rev`. Start with search_bergsonne if you do not know the identifier. When answering what a tile can DO in code, read `studio_unsupported` from get_driver: it lists chip capabilities the driver does not expose. Assuming a datasheet feature is reachable is the most common mistake made about this platform.
Known tools 8
search_bergsonneSearch everything Bergsonne publishes: tiles, tile drivers, individual driver functions, SDK symbols (core_/hal_/ll_), documentation pages, and the I²C/pad lookup tables.
Inferred read-onlylist_tilesEvery publicly available Bergsonne tile, with package, interfaces, primary part and links.
Inferred read-onlyget_tileThe full definition of one tile: package and real dimensions, onboard components with their vendor part numbers, power rails with voltage and current limits, every pad and its functions, and the interfaces with their I²C addresses.
Inferred read-onlyget_driverA tile driver's complete C API: every public function with its signature, parameters and return value, plus enums, structs and defines.
Inferred read-onlylist_driversEvery documented tile driver with its API size and — usefully — its count of declared capability gaps.
Inferred read-onlylookup_referenceThe two lookup tables, generated from the canonical tile definitions.
Inferred read-onlylist_shared_designsReal projects whose authors chose to publish them, showing which tiles get used together and how they are wired.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.bergsonne-knowledge]
url = "https://bergsonne.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"bergsonne-knowledge": {
"type": "http",
"url": "https://bergsonne.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: bergsonne-knowledge
Remote MCP URL: https://bergsonne.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"bergsonne-knowledge": {
"url": "https://bergsonne.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"bergsonne-knowledge": {
"type": "http",
"url": "https://bergsonne.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "bergsonne-knowledge",
"transport": "streamable-http",
"url": "https://bergsonne.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for bergsonne.io was fetched 2026-10-14T22:08:31.129Z.
bergsonne.io is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.