@apilium/altretta-bridge

One-command stdio bridge to your local Altretta second brain. For agents that speak MCP over stdio only (Codex CLI and compatibles); HTTP-native runtimes should point straight at the endpoint instead.

Use

npx -y @apilium/altretta-bridge --token <TOKEN>

Or set the token once and drop the flag:

export ALTRETTA_MCP_TOKEN=<TOKEN>       # or write it to ~/.altretta/mcp-token
npx -y @apilium/altretta-bridge

Create the token in the Altretta app: Settings, "AI & connections", "Access tokens". One token per agent: revoke one, the rest keep working.

Codex CLI example

~/.codex/config.toml:

[mcp_servers.altretta]
command = "npx"
args = ["-y", "@apilium/altretta-bridge"]
env = { ALTRETTA_MCP_TOKEN = "<TOKEN>" }

What it does

Resolves your token (argument, then ALTRETTA_MCP_TOKEN, then ~/.altretta/mcp-token) and runs mcp-remote against http://127.0.0.1:19191/mcp with the bearer header.

ALTRETTA_MCP_URL overrides the endpoint. Add a second entry pointing at http://127.0.0.1:19191/mcp-code to give a stdio agent Altretta's code tools too — the same token authorizes both.

If it fails to connect, either Altretta is not running, or it is running with no access token: revoking the last one leaves the endpoint closed until you create a new token and restart the app.

Part of the Altretta Skill. MIT licensed.