DriveBoard MCP Server

The custom MCP server authenticates every request with the caller's Base44 access token and then runs base44/shared/rbac.ts. Tools only return workspaces you own or belong to, plus projects shared with you. Filters narrow that slice. A foreign id is Forbidden, not an empty dump of another tenant. Platform admin does not bypass this.

If your client is still using Base44 App MCP entity CRUD tools (query_project and similar) on the same URL, those generated tools do not use this module. Prefer the custom tools (list_projects, list_tasks, …).

Find it in the Base44 dashboard:

Dashboard → Code → Functions → mcpServer → API / Webhook usage

It looks like:

https://driveboard.obriyx.com/api/mcp

The server exposes 15 tools covering the full project lifecycle:

Plus prompt templates: daily_standup, task_breakdown, project_status_report, sprint_planning.

Add the server to your client config as an HTTP server with a bearer token:

{
  "mcpServers": {
    "driveboard": {
      "type": "http",
      "url": "https://driveboard.obriyx.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_BASE44_ACCESS_TOKEN>"
      }
    }
  }
}

Your access token is the value in base44_access_token in the browser's localStorage after signing in. Treat it like a password.

• Per-user: the bearer token identifies the caller; RLS scopes every read and write.
• Never share your token publicly, and rotate it by logging out and back in.
• Destructive tools (delete_task) are annotated so clients prompt before running.