tally-mcp-install

One-command setup for the Tally HTTP MCP server across Cursor, OpenCode, Claude Code (CLI), and Claude Desktop (GUI).

Auth uses OAuth 2.1 — no API keys are stored in config files. On first connection, your MCP client will open a browser for you to sign in with your existing Tally account (Google/Apple).

Usage

Everything at once — Cursor, OpenCode, Claude Code (~/.claude.json), and Claude Desktop:

npx -y tally-mcp-install --all

Cursor only (default):

npx -y tally-mcp-install

Pick clients — combine flags as needed:

npx -y tally-mcp-install --with-opencode --with-claude-code
npx -y tally-mcp-install --with-claude

Single client:

npx -y tally-mcp-install --opencode-only
npx -y tally-mcp-install --claude-code-only

Then restart each app you updated. You'll be prompted to sign in via OAuth on first use.

Claude Code without this package: the official CLI can register the same server (docs):

claude mcp add --transport http --scope user \
  tally https://tallybudget.app/api/mcp

What it does

• Cursor: merges mcpServers.tally into ~/.cursor/mcp.json with a url pointing at the Tally MCP endpoint. OAuth is discovered automatically.
• OpenCode: merges mcp.tally into ~/.config/opencode/opencode.json with type: "remote" (see OpenCode remote MCP).
• Claude Code: merges mcpServers.tally into ~/.claude.json with type: "http" (Claude Code MCP).
• Claude Desktop: merges into mcpServers in the platform-specific Claude config file.
• Preserves unrelated keys in each file. Writes atomically (temp file + rename). Pure JSON only — if a config is JSONC with comments, merge manually or fix syntax first.

Publishing to npm (maintainers)

1. Log in: npm login

2. Ensure the package name tally-mcp-install is still available (or change name in package.json if you use a different unscoped name).

3. From this directory:

   npm publish

Security

• No secrets are written to config files. OAuth tokens are managed by the MCP client.
• The install script only writes a URL pointing to the Tally MCP endpoint.