# Theo · SDK & Open-Source Adapters

> Theo ships an open-source TypeScript SDK plus channel adapters for the popular chat platforms and a Model Context Protocol adapter. Open source by design: trust comes from the diff log, not the marketing copy.

Source of truth: https://hitheo.ai/for-developers. Last updated: 2026-05-24.

## Packages
- @hitheo/sdk. The official TypeScript SDK. Wraps the REST API, streaming, idempotency, and the structured response envelope.
- @hitheo/telegram. Telegram channel adapter. Mounts an AI Worker on a Telegram bot with one config object.
- @hitheo/whatsapp. WhatsApp channel adapter. Same shape as Telegram.
- @hitheo/mcp. Model Context Protocol adapter. Exposes Theo's tool surface as MCP tools so an MCP-aware client (IDE, agent runtime) can call Theo.

All four packages live in the public Theo monorepo and ship to npm. CI auto-publishes on a version bump.

## SDK quickstart (TypeScript)
```ts
import { Theo } from "@hitheo/sdk";

const theo = new Theo({ apiKey: process.env.THEO_API_KEY! });

// Streaming
const stream = await theo.completions.stream({
  prompt: "Draft a renewal letter for ICHRA policy 12345.",
  mode: "auto",
  metadata: { conversationId: "conv_abc" },
});

for await (const event of stream) {
  if (event.type === "token") process.stdout.write(event.text);
  if (event.type === "artifact") console.log("artifact:", event.url);
}

// Non-streaming
const result = await theo.completions.create({
  prompt: "Summarize the attached PDF.",
  mode: "auto",
});
console.log(result.text);
```

## Channel adapters
Channel adapters bind a Theo API key to a chat platform and translate platform-specific message events into Theo completion calls. They handle media attachments, thread continuity, and platform-specific edge cases (delivery receipts, edit windows).

Telegram example:
```ts
import { TelegramAdapter } from "@hitheo/telegram";

new TelegramAdapter({
  apiKey: process.env.THEO_API_KEY!,
  botToken: process.env.TELEGRAM_BOT_TOKEN!,
}).listen();
```

## Model Context Protocol adapter
@hitheo/mcp exposes Theo's tool surface (memory ops, generation, research, document creation, browser) as MCP-compliant tools. An MCP-aware IDE or agent runtime can call Theo without going through the REST API directly.

## Versioning and stability
The SDK follows semver. Breaking changes ship under a major version bump. The REST API has its own version header (Theo-Api-Version). The SDK pins to a known-stable version by default and accepts overrides per call.

## Related machine-readable files
- https://hitheo.ai/llms.txt — full index of every Theo machine-readable file.
- https://hitheo.ai/llms-full.txt — long-form knowledge bundle (single fetch).
- https://hitheo.ai/humans.txt — team and open-source credits.
- https://hitheo.ai/lawyers.txt — trademark notice and legal contact.
- https://hitheo.ai/.well-known/security.txt — security disclosure contact.