TIMPush Model Context Protocol (MCP) Server for AI IDEs

This package provides a CLI-based Model Context Protocol (MCP) server that helps AI agents integrate and troubleshoot Tencent Cloud TIMPush (offline push) on Android, iOS, Flutter, and uni-app.

Features

• Detect Android, iOS, Flutter, and uni-app project layouts relevant to TIMPush.
• Fetch vendor setup guides and validate credentials / package-name consistency.
• Compute Android signing SHA-256 fingerprints via local keytool (passwords are not echoed or persisted).
• Drive guided wizard and troubleshoot workflows over stdio MCP.
• Analyze IM SDK xlog / decoded logs for TIMPush registration and offline-push evidence (independent of workflows).
• Works with Cursor, Claude Code, CodeBuddy, and other MCP-compatible AI IDEs.

Prerequisites

• Node.js (>= 18.17) and npm
• An AI IDE with MCP support

How To Use

To set up @tencent-rtc/trtc-push-mcp, follow these steps:

Step 1: Installation

npx -y @tencent-rtc/trtc-push-mcp@1

Pin a major (or minor) version in MCP config to avoid unexpected upgrades, for example @1 or @1.0.

Step 2: Add MCP config

Cursor (project .cursor/mcp.json or ~/.cursor/mcp.json):

{
  "mcpServers": {
    "trtc-push-mcp": {
      "command": "npx",
      "args": ["-y", "@tencent-rtc/trtc-push-mcp@1"]
    }
  }
}

Project-level servers (.cursor/mcp.json) are disabled by default and recent Cursor versions show no prompt — toggle on trtc-push-mcp via the Cursor sidebar → Customize → MCP, then reload the window. User-level servers (~/.cursor/mcp.json) are enabled automatically.

Claude Code (project .mcp.json or ~/.claude.json → mcpServers):

{
  "mcpServers": {
    "trtc-push-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@tencent-rtc/trtc-push-mcp@1"]
    }
  }
}

Or:

claude mcp add trtc-push-mcp -- npx -y @tencent-rtc/trtc-push-mcp@1

Project .mcp.json servers need approval: Claude Code asks on the first session in the project, or approve later via /mcp. To pre-approve, add "enabledMcpjsonServers": ["trtc-push-mcp"] to .claude/settings.local.json.

CodeBuddy (project .mcp.json in the project root — auto-enabled, works for both the CodeBuddy IDE and CLI):

{
  "mcpServers": {
    "trtc-push-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@tencent-rtc/trtc-push-mcp@1"],
      "description": "TIMPush integration helper for push setup."
    }
  }
}

Reload the IDE after saving. (User-level setup via Settings → MCP → Add MCP also works.)

Codex (project .codex/config.toml):

[mcp_servers.trtc-push-mcp]
command = "npx"
args = ["-y", "@tencent-rtc/trtc-push-mcp@1"]

Codex loads project config only after you trust the project — run codex in the project and accept the trust prompt.

Step 3: Confirm the server is enabled

Open your IDE MCP settings and verify that trtc-push-mcp is listed and enabled. Note the per-IDE behavior above: Cursor disables project-level servers until you toggle them on; Claude Code requires approval unless pre-approved; CodeBuddy auto-enables the project .mcp.json; Codex requires project trust.

Step 4: Ask the AI agent

Describe what you need, for example:

• Help me integrate TIMPush on Android
• iOS offline push is not received
• Set up Huawei / Xiaomi / FCM vendor push with TIMPush
• Decode and analyze this IM SDK xlog for push registration

IM SDK log analysis (standalone)

Independent tools; in troubleshoot workflows they are used only at stage-7 when prior evidence cannot locate a root cause (not at kickoff).

Typical flow:

1. get_imsdk_log_guide — how to enable logging and where files live. Hard requirement for users: reproduce → restart the app → login IM SDK again → then export *.xlog (otherwise logs are incomplete).
2. decode_imsdk_xlog — decompress a local .xlog with bundled Python scripts. Requires local Python 3; on failure returns manual decode steps.
3. analyze_imsdk_push_log — extract TIMPush / offline-push evidence. Files larger than 500KB require a time_range.

Logs are read locally only; contents are not uploaded or persisted by the MCP.

Credential safety

Sensitive values are handled in memory only: they are not printed, persisted by the MCP, or uploaded as credentials. Write tools default to dry-run until you pass confirm: true.

Reporting issues

• Bugs and feature requests: use the public issue channel from the agent-skills / TIMPush suite you installed with.
• Security issues: follow the Tencent Cloud security response process. Do not paste SDKAppID, AppKey, APNs certificates, or local.properties / timpush.local.xcconfig contents in public issues.

Anonymous product usage metrics may be collected to improve reliability; ask support if you need to disable them.

Contact Us

Need technical support or enterprise pricing? Submit your contact information at trtc.io/contact and our team will get back to you shortly.