Start

Get Started

Install the package, point your assistant at the MCP server, and start from a working example. Each step below stands on its own — the first is all you need to write code, and the SDK itself needs no key, no account and no network.

1. Install TheTowerSDK

Add the package to your app or tool repo. Pin a version when you want frozen game numbers.

npm install thetowersdk

Package: npmjs.com/package/thetowersdk · source: GitHub

2. Register The MCP Server

Point Cursor, Claude Code, or Copilot at the package MCP server. Your assistant can then list exports, read catalogs, decode saves, plan Effective Paths, and pull wiki pages while it works.

{
  "mcpServers": {
    "thetowersdk": {
      "command": "node",
      "args": ["./node_modules/thetowersdk/mcp/server.mjs"]
    }
  }
}

Put that under your editor’s MCP config (for example Cursor .mcp.json or the IDE MCP settings). Restart the IDE MCP session after saving. Docs: MCP & AI.

3. Explore The Examples

Every example on this site runs against the installed package. Open one, copy it, and change the inputs — the numbers move because they come from the catalogs, not from a fixture.

Examples — runnable snippets, grouped by task
What You Can Build — finished tool shapes, each linked to its docs
Docs — the full reference, one page per area

4. Saves From a Device (optional)

Android path: Android/data/com.TechTreeGames.TheTower/files/playerInfo.dat. adb-bridge can copy it from a device or emulator. Decode with thetowersdk/node, then extractors in thetowersdk/save.

5. What You Can Add Alongside It

None of these are dependencies. The SDK works on its own, offline, with no keys — each of these adds one capability it deliberately does not carry itself.

TowerAI — an assistant that answers from a knowledge base

npm install towerai. The SDK holds the numbers; TowerAI does retrieval over a knowledge base you curate and prompts a model with what it found, so answers cite something instead of being invented. You bring the model key — a free one from console.groq.com is enough to run it.

TowerAI docs → · GitHub · npm

adb-bridge — read a save off a phone or emulator

npx adb-bridge. The SDK decodes save bytes; getting those bytes off an Android device is a separate job, and this is it. Your users run it on their own machine — it is not a dependency of your project, and nothing about it ships to them through you.

Save docs → · GitHub · npm

discord.js — every calculator as a slash command

thetowersdk/bot turns the builders into commands and replies and never touches a Discord client, so it is transport-agnostic. Add discord.js when you want those commands on a server.

Discord bot docs →

google-auth-library — read and write spreadsheets

thetowersdk/sheets takes a transport you supply and imports no Google library itself, so nothing about your auth is assumed. For an unattended tool, a service account is the identity to use.

Spreadsheet docs →

6. Ready To Build

Examples

Interactive demos and sample imports.

Open Examples →

Example Product

The Tower Run Tracker ships calculators and trackers on this package.

What You Can Build →