familybugle-mcp
A stdio bridge to the hosted Family Bugle MCP connector, for hosts that can only launch a command.
Most hosts do not need this. Claude, ChatGPT and Cursor all connect to a
remote MCP server directly, and connecting to https://familybugle.com/mcp
is the better path: fewer moving parts, nothing to install, nothing to keep
up to date. Reach for this package only when your host cannot do that.
What it does
It forwards. tools/list, tools/call, prompts and resources all go
straight to the hosted connector and come back untouched, so this package
exposes exactly what production exposes — 15 catalog tools that need no
account, and 8 account tools behind OAuth 2.1.
That is a deliberate design rather than a shortcut. Until v0.2.0 this package was a second implementation of the catalog against the public REST API, and it drifted: four of its five tool names no longer existed on the server, so the package ran fine and called nothing. A bridge has no second copy to fall behind.
Install
No installation required:
uvx familybugle-mcp
Claude Desktop
{
"mcpServers": {
"familybugle": {
"command": "uvx",
"args": ["familybugle-mcp"]
}
}
}
Cursor
{
"mcpServers": {
"familybugle": {
"command": "uvx",
"args": ["familybugle-mcp"]
}
}
}
Signing in
The 15 catalog tools work anonymously. The 8 account tools — profile, children, digest and email preferences — need a signed-in user, and this bridge does not run an OAuth flow of its own.
If your host supports remote MCP, connect to https://familybugle.com/mcp
directly and sign in there; the hosted connector prompts for sign-in when a
conversation first reaches an account tool.
Otherwise, set a Supabase access token and the bridge sends it upstream:
FAMILYBUGLE_TOKEN="<access token>" uvx familybugle-mcp
Without it the account tools refuse, which is the server's own behaviour rather than anything this package adds.
The token is read once at startup and never refreshed. A Supabase access token lasts about an hour; after that the account tools fail until you restart the command with a fresh one. The bridge holds no refresh token and cannot ask for one. If your host can reach the remote connector, sign in there instead — it handles this for you.
Configuration
| Variable | Default | Purpose |
|---|---|---|
FAMILYBUGLE_MCP_URL |
https://familybugle.com/mcp |
Connector URL to bridge to |
FAMILYBUGLE_TOKEN |
unset | Optional bearer token for the account tools |
Tool reference
The current tool list is whatever the connector answers, and is documented at https://familybugle.com/ai/reference/mcp.
Development
uv run pytest -q
uv run ruff check src tests
License
MIT
Metadata
Release files for familybugle-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| familybugle_mcp-0.2.0.tar.gz | 49.7 kB | With provenance | Details for familybugle_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| familybugle_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for familybugle_mcp-0.2.0-py3-none-any.whl |
Total release size: 56.0 kB
Release files / familybugle_mcp-0.2.0.tar.gz
| Download URL | familybugle_mcp-0.2.0.tar.gz |
|---|---|
| Size | 49.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d054c1db3bef32bb957cb1f1dee91108a5c709d78e5d8ab66bbc957e0c120232
|
|
BLAKE2b-256 checksum How to use checksums |
910d0b6b56ee4aa9b68b6459974119043e1477ccd6c99171e0dec0154649f1fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logRelease files / familybugle_mcp-0.2.0-py3-none-any.whl
| Download URL | familybugle_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0977639d54d8dea5cc41b92ca231d440da91e988a3e0029c7b52c56de4a2987
|
|
BLAKE2b-256 checksum How to use checksums |
b16b60eaf8cf9a941a3f4a61b3e2ed9e9a96e3a11ee87a5c810918ce288bc5ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logSecurity for familybugle-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for familybugle_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.