The Bridge

Your library, inside your tools

Mint a personal token, then your prompts, handovers, and contract are reachable from Claude Code, Cursor, any MCP client, and the plain terminal. The token is shown once and only its fingerprint is stored.

1 · Mint a token

2 · Claude Code / any MCP tool

One command connects it. Then ask the agent for “my latest handover” or “the prompt called X” and it pulls straight from here.

claude mcp add fullauthority --transport http https://xjyopakfmhgtzwqchluw.supabase.co/functions/v1/bridge/mcp --header "Authorization: Bearer fa_YOUR_TOKEN"

Cursor / Windsurf: add the same URL + header in their MCP settings. Tools exposed: search_prompts, get_prompt, save_prompt, latest_handover, save_handover, get_contract.

3 · The terminal (fa)

A single small script, no install chain.

curl -fsSL https://fullauthority.app/fa -o /usr/local/bin/fa && chmod +x /usr/local/bin/fa

export FA_TOKEN={your token}
fa get "the scope fence"     # fetch a prompt by title
fa save < prompt.txt         # save from stdin
fa handover save < notes.md  # end-of-session handover
fa handover load             # pick it up anywhere

An npm package and direct GitHub / Slack / Discord connectors are coming; the script and MCP work today.

How this stays safe

Shown once, stored as a fingerprint. We keep only a one-way hash of your token, never the token itself. Nobody, including us, can read it back.
Only your data, ever. A token reaches exactly your prompts, handovers, and contract. It cannot see another person’s library, or anything else in the app.
Revoke instantly. Tap Revoke and that token stops working immediately, everywhere. Lost a laptop? Cut it and mint a new one.
Kept out of your shell history. The fa script reads the token from an environment variable, never a command argument, so it never lands in logs or ps.
You choose what leaves. The Bridge reads and writes only when a tool asks; nothing is uploaded in the background, and there is no telemetry on your prompt content.