Find features you built in other projects, see how they fit this one, and reuse them.
Connect Runs on your machine
claude mcp add brico -e BRICO_TOKEN=<BRICO_TOKEN> -- npx -y [email protected]
{
"mcpServers": {
"brico": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRICO_TOKEN": "<BRICO_TOKEN>"
}
}
}
}
{
"mcpServers": {
"brico": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRICO_TOKEN": "<BRICO_TOKEN>"
}
}
}
}
{
"servers": {
"brico": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRICO_TOKEN": "<BRICO_TOKEN>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
BRICO_TOKENOptional, secret | Your BRICO Builder invite token (bt_…). Optional if you ran `brico login`. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 28 Oct 2026 |
| Last updated | 28 Oct 2026 |
| Registry name | io.github.ScienceWerx-Inc/brico |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
