Technical
MCP and API
Hosted MCP, custom tools, retrieval profiles, tokens, activity, inspector, playground, and API integration guidance for connecting CaveauAI to external AI clients.
Public and internal interfaces
These are the main routes, handlers, and integration surfaces used by this product area.
GET/POST /api/portal/mcp/config
GET/POST/PATCH/DELETE /api/portal/mcp/profiles
POST /api/portal/mcp/profiles/{id}/test
GET/POST/DELETE /api/portal/mcp/tokens
GET /api/portal/mcp/usage
GET/POST/PATCH/DELETE /api/portal/mcp/tools
GET/POST /api/portal/mcp-inspector
Hosted endpoint: https://mcp.caveauai.bluenotelogic.com/mcp
Architecture notes
- The React page imports markdown help from caveauai-web/src/help/mcp.
- The portal handler manages config, profiles, tokens, tools, usage, and n8n integration.
- The hosted Node MCP server lives in caveau-mcp and speaks modern Streamable HTTP.
- MCP calls are authenticated with X-MCP-Token and logged to usage tables.
Access and permissions
App pages are authenticated through the shared bnl_session cookie unless explicitly marked public. Public docs should describe integration behavior without including secrets, private tokens, private IPs, or tenant-specific records.
Troubleshooting
- HTTP 401 means the MCP token is missing, wrong, or revoked.
- HTTP 403 usually means the plan does not include MCP.
- If a tool returns unexpected output, test it from the Tools tab before using it from Claude.