Skip to main content
Glama
Board as a Service

Board as a Service

by profullstack

Board as a Service

https://board.saas.pit.world (Moshpit name board.saas)

Paste a decision brief. Five AI advisors give independent verdicts, debate each other by name, and a chair writes the minutes: the vote, where they clashed, the strongest dissent, a recommendation and the one question you still need to answer. You get an interactive report at a shareable link, downloadable as one HTML file.

The advisors are AI models running on the c0mpute peer network. They are not real directors, and nothing here is legal, tax or investment advice.

It productizes the open-source boardroom Claude Code plugin: the expert personas are its skill texts (src/experts/*.md), the meeting follows its commands/meet.md, and the report is its render-report.mjs.

The board

id

Member

Lens

cfo

The CFO

cash, runway, unit economics, payback

growth

The Growth Marketer

audience, distribution, revenue growth

operator

The Operator

systems, delegation readiness, execution

founder-time

The Founder-Time Strategist

founder hours, highest-value work

contrarian

The Contrarian Investor

inversion, reversibility, opportunity cost

The chair runs the meeting and never votes.

Related MCP server: mcp-consensus

How a meeting runs

  1. Brief check. The chair extracts the decision, options and constraints. If one is missing it asks once (needs_clarification); anything still missing becomes a written assumption.

  2. Verdicts. Five calls in parallel; each sees only the brief.

  3. Debate. Five calls in parallel; each reads all five named verdicts.

  4. Minutes. One chair call. The vote table is built from what each member said.

Every answer is JSON, validated per round, retried once with the error spelled out. If c0mpute cannot answer, the meeting fails with the real error and is refunded. There is no paid-model fallback in the code at all.

Pricing

First meeting free per email address, then $9 per meeting through CoinPay (crypto).

Surfaces

All four are thin clients over the same HTTP API.

# CLI
npm i -g @profullstack/board-saas        # or: curl -fsSL https://board.saas.pit.world/install.sh | sh
board-saas login                         # OAuth device code: open the link, type the code (works over ssh)
board-saas login you@example.com         # or an emailed code and an API key
board-saas meet "Decision: ... Options: ... Constraints: ..." --data financials.txt --out report.html
board-saas get <id> | list | clarify <id> "<answers>" | report <id>
board-saas connections | disconnect <client_id> | logout

# TUI
board-saas tui

# MCP (tools: run_meeting, get_meeting, list_meetings, clarify_meeting, get_account)
claude mcp add --transport http board-saas https://board.saas.pit.world/mcp   # OAuth: signs in in your browser
# claude.ai / ChatGPT: add https://board.saas.pit.world/mcp as a custom connector
claude mcp add --transport http board-saas https://board.saas.pit.world/mcp --header "Authorization: Bearer $BOARD_SAAS_KEY"   # or a key
claude mcp add board-saas -- npx -y @profullstack/board-saas mcp      # stdio

# HTTP API: https://board.saas.pit.world/api/v1
curl -X POST https://board.saas.pit.world/api/v1/auth/code -H 'content-type: application/json' -d '{"email":"you@example.com"}'
curl -X POST https://board.saas.pit.world/api/v1/auth/verify -H 'content-type: application/json' -d '{"email":"you@example.com","code":"123456"}'
curl -X POST https://board.saas.pit.world/api/v1/meetings -H "Authorization: Bearer $BOARD_SAAS_KEY" -H 'content-type: application/json' -d '{"brief":"..."}'
curl https://board.saas.pit.world/api/v1/meetings/<id>

OAuth 2.1 and your company data

board.saas is its own OAuth 2.1 authorization server, so any OAuth client can act for an account: the Claude and ChatGPT connectors, claude mcp add without a header, the CLI, or your own app. The same access token works on /mcp and /api/v1.

What

Where

Server metadata (RFC 8414)

/.well-known/oauth-authorization-server

Resource metadata (RFC 9728)

/.well-known/oauth-protected-resource/mcp (resource = the /mcp URL), /.well-known/oauth-protected-resource/api/v1

Dynamic client registration (RFC 7591)

POST /oauth/register (also POST /register); public clients, or client_secret_post / client_secret_basic

Authorization code + S256 PKCE

GET /oauth/authorize (consent page with inline email-code sign-in), iss on every redirect

Token

POST /oauth/token: authorization_code, refresh_token (rotated; a replayed one revokes the connection), urn:ietf:params:oauth:grant-type:device_code

Device flow (RFC 8628)

POST /oauth/device_authorization, the person types the code at /oauth/device; client id board-saas-cli

Revocation (RFC 7009)

POST /oauth/revoke; or GET/DELETE /api/v1/connections[/:client_id]

One scope, board: run, read, list and clarify the account's meetings, spending its free meeting or paid credits. Access tokens last an hour, refresh tokens 90 days.

Company data. run_meeting (MCP) and POST /api/v1/meetings take company_data (text or JSON, up to 12,000 characters) that every advisor reads with the brief. In an agent connected to both board.saas and your books (QuickBooks, CoinPay, Stripe), the agent pulls the P&L, cash, runway, MRR and churn and hands them over, so the CFO argues from your real numbers. The data never appears on the shareable report.

Running it

Node 22.6+ (uses node:sqlite). Configuration comes from the logicsrc vault profullstack/board-saas--prod (synced into an env file by deploy/deploy.sh): C0MPUTE_API_KEY, C0MPUTE_MODELS, RESEND_API_KEY, BOARD_SAAS_ADMIN_KEY, COINPAY_API_URL, COINPAY_BUSINESS_ID, COINPAY_API_KEY, COINPAY_WEBHOOK_SECRET. Optional: C0MPUTE_CONCURRENCY (parallel c0mpute calls, default 2), C0MPUTE_SITE_URL (the c0mpute-hosted copy of the front page), PORT, BOARD_DB, PUBLIC_URL.

npm install
npm test
node scripts/build-static.mjs   # ./site, footers baked in; published to c0mpute hosting
node src/server.js

Hosting: the front page is published on the c0mpute network (three self-healing copies) and served at board.saas.pit.world by the app, which proxies it with its own build as the fallback. The API, MCP endpoint and meeting runner are a systemd unit on dev2 behind the Moshpit origin (deploy/).

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that implements an advisor-based consensus mechanism for collaborative problem-solving using multiple AI models, enabling structured discussion and debate among 5 specialized advisors to reach optimal solutions.
      1
      27 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Multi-model AI council MCP server that lets multiple LLMs debate, critique, and vote on questions to reach a consensus, with automatic failover and hot-swap of models during debates.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run structured multi-persona debates over high-stakes decisions and merge their positions into an explainable consensus, complete with logged dissenting minority opinions. It runs as a zero-dependency Python MCP server or importable module, compatible with Claude Desktop, Cursor, and custom agent frameworks.
      7
      MIT