Overview
Nibbo integration documentation — who it is for and how to navigate it.
Nibbo is a family home CRM (nibbo.space): shared tasks, calendar, notes, shopping, budget, subscriptions, and more. Everything important is scoped to a family so only members of that household see the data.
This site documents machine-facing HTTP APIs only: how to authenticate, which URLs to call, and what they return. It does not replace in-app help for end users.
Who should read this
| Audience | Start here |
|---|---|
| Developers building scripts, dashboards, or bridges | Authentication, then REST API v1 or MCP read |
| Operators wiring server-side tools (e.g. env-based tokens) | Authentication → env NIBBO_MCP_READ_TOKENS on MCP read |
| Anyone needing the mental model of the app | Architecture |
How this documentation is organized
| Section | Contents |
|---|---|
| Guides | Architecture — how the app, sessions, and tokens fit together. Authentication — profile toggle, scopes, creating and revoking keys. |
| API reference | REST API v1 — Bearer endpoints under /api/v1. MCP (HTTP read) — read-only /api/mcp/read/... and optional env tokens. |
Stack (for context)
- Next.js (App Router), Prisma, PostgreSQL
- NextAuth — browser sessions use cookies; integrations use Bearer tokens issued from the profile
Source code lives on GitHub: BostonLeeK/nibbo.
Base URL for examples
BASE_URL is the origin of the Nibbo deployment (scheme + host, no path). Production: https://nibbo.space. Local dev is often http://localhost:3000.
export BASE_URL=https://nibbo.spaceReplace YOUR_TOKEN in snippets with a real key from your profile. Keys are shown once when created — store them in a secret manager or env file, not in git.