Chat to APIChat to API
Local-first chat bridgeWeChat & Telegram · macOS & Windows

Turn your desktop chat history into a controllable API.

Local-first chat bridge for AI agents and automated workflows. Native support for WeChat local decryption and Telegram MTProto live sync, serving clean context over standard REST and MCP protocols.

View client statusOpen Console
WeChat Local Read-Only
Telegram MTProto Live
MCP-Compatible
Native macOS & Windows
Encrypted Relay
chattoapi-gateway
{
  "mcpServers": {
    "chat-to-api": {
      "url": "http://127.0.0.1:18765/mcp",
      "headers": {
        "Authorization": "Bearer <LOCAL_API_KEY>"
      }
    }
  }
}
Two adapter implementations

Chat platform adapters

WeChat and Telegram adapters use unified /v1 REST and MCP endpoints. Source databases stay on your device; remote access is optional.

WeChat

Local Read-Only Snapshot

Directly reads encrypted local SQLite database snapshots and decrypts them strictly in memory. Never writes plaintext to disk and never disrupts the official app.

  • In-memory read-only SQLite / WCDB decryption
  • Structured parsing for contacts, groups, and chats
  • Secure extraction of text, audio, images, and files
  • Verified on macOS WeChat 4.1.13 & Windows WeChat 4.1.15

Telegram

MTProto development preview

A local MTProto adapter implements phone/code authentication, 2FA, and incremental message updates. Real-account acceptance is pending.

  • Native local MTProto connection
  • Phone SMS code & 2FA password authentication
  • Real-time message streaming & incremental cursors
  • macOS & Windows implementation; real-account checks pending
More Chat Platforms Coming SoonRoadmap

Adapters for iMessage, WhatsApp, Slack, and other platforms are on our roadmap, following the same unified API contract.

Desktop client release status

Desktop clients support WeChat local read-only decryption and Telegram live protocol syncing; signed macOS and Windows release packages are undergoing acceptance.

macOS Client

Development preview
✓ WeChat✓ Telegram (MTProto)

WeChat 4.1.13 encrypted snapshots were verified on macOS. A Telegram MTProto adapter is implemented; real-account acceptance is pending. Requires macOS 14 or later.

Code and local tests are available; public signing and notarization are pending.

Windows Client

Development preview
✓ WeChat✓ Telegram (MTProto)

WeChat 4.1.15 text records were verified on a target Windows machine. Telegram real-account, installer, and wider compatibility checks are pending.

Code and local tests are available; the Windows release package is pending.

Public downloads will appear after signing, compatibility, and installation checks are complete.

Disclaimer

Capabilities

Built for AI developers and power users

Bridge desktop chat databases into controllable APIs with zero compromise on privacy.

Dual-Platform Native Clients

Dedicated native desktop clients for macOS and Windows, protecting keys with system credential stores while keeping source databases local.

WeChat & Telegram Integration

Simultaneously supports read-only decryption of local WeChat databases and live MTProto protocol streaming with incremental syncing for Telegram.

Granular Scopes & Time Boundaries

Select specific conversations, contact lists, and time windows. Issue distinct, isolated API keys for each agent or workflow.

MCP-Compatible Interface

The desktop clients include a local Model Context Protocol endpoint for seamless integration with Cursor and Claude Desktop.

Secure Encrypted Relay

Clients can establish an outbound WebSocket to the deployed relay; production desktop validation is pending.

Cross-Platform Unified Search

Unified keyword search, context tracking, and keyset-based cursor pagination across both WeChat and Telegram sources.

Architecture and access

End-to-End Privacy & Local-First Architecture

Privacy-first by design: databases stay local, keys are never shared, and outbound-only relay avoids exposing ports.

Your device (WeChat SQLite / Telegram MTProto)Local
Source database remains encrypted
Telegram · MTProto development preview
Read-only local queries
Keychain / DPAPI credentials
Outbound WebSocket
No inbound port required
Optional cloud relayDevelopment
Forwards authorized queries
Processes responses in transit
REST and MCP gateway
REST / MCP
Bearer token and scopes
AI tools and scriptsClient
MCP-compatible clients
Desktop integrations
Custom automation
01Local

1. Multi-Source Local Decryption & Sync

WeChat opens local encrypted databases read-only in memory; Telegram establishes local MTProto live sync. Zero plaintext disk export, zero disruption to official apps.

02Outbound

2. Outbound Encrypted Relay (WSS)

The optional client connects over an outbound WebSocket. The production relay is deployed; desktop end-to-end checks are pending.

03Scoped

3. Scoped Remote Access

Granular token and conversation permissions passed development tests. Production client validation is ongoing.

04Export

4. Batch Export & Knowledge Pipeline

Batch export filtered threads into Markdown, text, or structured JSON for training datasets or offline archives.

FAQ

Frequently Asked Questions

Everything you need to know about security, privacy, and architecture.

Development preview

Explore the Chat to API development preview

Review the current client status and supported versions before trying a development build.

View client statusOpen Console