telegram-ads-mcp 0.1.0 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +11 -6
  2. package/package.json +4 -3
package/README.md CHANGED
@@ -6,6 +6,7 @@
6
6
 
7
7
  <p align="center">
8
8
  <a href="https://github.com/furkankoykiran/telegram-ads-mcp/actions/workflows/ci.yml"><img src="https://github.com/furkankoykiran/telegram-ads-mcp/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
9
+ <a href="https://registry.modelcontextprotocol.io/?q=io.github.furkankoykiran%2Ftelegram-ads"><img src="https://img.shields.io/badge/MCP%20Registry-listed-6f42c1" alt="MCP Registry"></a>
9
10
  <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License: MIT"></a>
10
11
  <a href="https://nodejs.org"><img src="https://img.shields.io/badge/node-%3E%3D22.18-339933?logo=node.js&logoColor=white" alt="Node.js 22.18 or newer"></a>
11
12
  <a href="https://www.typescriptlang.org"><img src="https://img.shields.io/badge/TypeScript-strict-3178C6?logo=typescript&logoColor=white" alt="TypeScript strict"></a>
@@ -49,17 +50,18 @@ targeting from Claude, Cursor, Codex, OpenCode or any MCP-compatible client.
49
50
 
50
51
  ### 1. Connect the server
51
52
 
52
- The package name is `telegram-ads-mcp`. Until the first npm release is available, install straight
53
- from GitHub; npm builds the package automatically:
53
+ The package is published on npm as `telegram-ads-mcp` and listed in the official
54
+ [MCP Registry](https://registry.modelcontextprotocol.io/?q=io.github.furkankoykiran%2Ftelegram-ads)
55
+ as `io.github.furkankoykiran/telegram-ads`. Run:
54
56
 
55
57
  ```bash
56
- npx -y github:furkankoykiran/telegram-ads-mcp doctor
58
+ npx -y telegram-ads-mcp doctor
57
59
  ```
58
60
 
59
- After the npm release, the shorter form works too:
61
+ To run the latest commit from GitHub instead of the npm release, use:
60
62
 
61
63
  ```bash
62
- npx -y telegram-ads-mcp doctor
64
+ npx -y github:furkankoykiran/telegram-ads-mcp doctor
63
65
  ```
64
66
 
65
67
  Or build a local checkout:
@@ -85,7 +87,7 @@ npx -y telegram-ads-mcp init --client opencode --token <your-token>
85
87
  npx -y telegram-ads-mcp init --client all --token <your-token>
86
88
  ```
87
89
 
88
- Before the npm release, add `--github` so the generated config launches the GitHub package instead:
90
+ To launch the GitHub package instead of the npm release, add `--github`:
89
91
 
90
92
  ```bash
91
93
  npx -y github:furkankoykiran/telegram-ads-mcp init --client all --github --token <your-token>
@@ -397,6 +399,9 @@ The method catalog is generated from <https://ads.telegram.org/docs/api>. If Tel
397
399
  API revision, run `npm run sync-catalog`, review the diff and update the tools that need new fields.
398
400
  Do not edit `src/api/catalog.ts` by hand.
399
401
 
402
+ Release steps and the one-time trusted publishing setup are documented in
403
+ [docs/releasing.md](docs/releasing.md).
404
+
400
405
  ## Troubleshooting
401
406
 
402
407
  | Symptom | Fix |
package/package.json CHANGED
@@ -1,6 +1,7 @@
1
1
  {
2
2
  "name": "telegram-ads-mcp",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
+ "mcpName": "io.github.furkankoykiran/telegram-ads",
4
5
  "description": "Open-source MCP server for the official Telegram Ads API. Manage accounts, ads, stats, audiences, pixels, and targeting from Claude, Cursor, Codex, and other AI agents.",
5
6
  "author": "Furkan Koykiran",
6
7
  "license": "MIT",
@@ -14,8 +15,8 @@
14
15
  }
15
16
  },
16
17
  "bin": {
17
- "telegram-ads-mcp": "./dist/cli.js",
18
- "tg-ads-mcp": "./dist/cli.js"
18
+ "telegram-ads-mcp": "dist/cli.js",
19
+ "tg-ads-mcp": "dist/cli.js"
19
20
  },
20
21
  "files": [
21
22
  "dist",