Package Exports
- brcks-mcp
- brcks-mcp/dist/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (brcks-mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
BRCKS MCP Server
Manage your construction projects from Claude, ChatGPT, or any AI assistant.
BRCKS works wherever you work — WhatsApp, Telegram, the app, or your AI assistant. One brain, every channel.
Quick Setup (Claude Desktop)
Install globally:
npm install -g brcks-mcp
Add to your Claude Desktop config (
~/Library/Application Support/Claude/claude_desktop_config.json):{ "mcpServers": { "brcks": { "command": "brcks-mcp", "env": { "BRCKS_EMAIL": "your@email.com", "BRCKS_PASSWORD": "your-password" } } } }
Restart Claude Desktop.
Say "What's happening on my sites?" and Claude will connect to your BRCKS account.
Setup (Claude Code)
Add to your Claude Code MCP config:
{
"mcpServers": {
"brcks": {
"command": "npx",
"args": ["brcks-mcp"],
"env": {
"BRCKS_EMAIL": "your@email.com",
"BRCKS_PASSWORD": "your-password"
}
}
}
}What You Can Do
| Say this... | BRCKS does this |
|---|---|
| "List my projects" | Shows all active projects with stats |
| "What happened at Riverside today?" | Gets project updates and daily digest |
| "Mark the kitchen tiling as done, took 3 hours" | Completes the task and logs hours |
| "Send this photo to the Riverside project" | Attaches the image to a project update |
| "Who's on site at Cheyne Gardens?" | Shows the project team |
| "Create a task for Stuart: fit the bathroom extractor" | Creates and assigns the task |
| "What's my schedule this week?" | Shows upcoming calendar events |
| "Give me a summary of all my sites" | Generates a morning briefing |
| "When was the roof completed at Riverside?" | Searches project history with AI |
| "Show me the site diary for yesterday" | Gets the auto-generated site diary |
| "What files do we have for Riverside?" | Lists project documents and drawings |
Available Tools
Core
brcks_list_projects— List all active projectsbrcks_get_project— Get detailed project infobrcks_create_update— Post an update (with optional images)brcks_list_tasks— View tasks for a projectbrcks_complete_task— Mark a task as donebrcks_create_task— Create a new taskbrcks_get_schedule— View calendar eventsbrcks_create_event— Create a calendar eventbrcks_search— Search all project data (Ask BRCKS)brcks_get_digest— Get the daily digestbrcks_get_team— View project team membersbrcks_get_files— List project filesbrcks_get_site_diary— Get the site diarybrcks_morning_briefing— Get the morning briefing
Environment Variables
| Variable | Required | Description |
|---|---|---|
BRCKS_EMAIL |
Yes | Your BRCKS account email |
BRCKS_PASSWORD |
Yes | Your BRCKS account password |
SUPABASE_URL |
No | Override Supabase URL (default: BRCKS production) |
SUPABASE_ANON_KEY |
No | Override anon key (default: BRCKS production) |
Security
- Your credentials are stored locally in your MCP client config — never transmitted to third parties
- All data access uses Supabase Row Level Security (RLS) — same as the BRCKS app
- The MCP server runs locally on your machine
- No data is cached or stored outside of Supabase
Licence
Proprietary — BRCKS Ltd.