Telecomsxchangeapi Destinations Api Claude Plugin
- 1 repo stars
- Updated October 12, 2025
- TelecomsXChangeAPi/destinations-api-claude-plugin
telecomsxchangeapi-destinations-api-claude-plugin is a Claude Code plugin that connects agent-assisted development to the Destinations API global telecom MCC/MNC and numbering database.
About
telecomsxchangeapi-destinations-api-claude-plugin is the official Claude Code marketplace wrapper for the Destinations API, a global telecommunications database used when you code products that reason about countries, carriers, mobile network codes, and standardized phone identifiers. developers shipping MVNO tools, SMS gateways, fraud scoring, or billing dashboards often stall on correct MCC/MNC and E.164/E.212 mapping; this plugin lets your agent reference that dataset while you scaffold API clients, validation rules, and integration tests in the Build phase. It is narrowly telephony-oriented—not a general geolocation or payments plugin—so value appears when your backlog explicitly mentions operators, destinations, or numbering plans. Install it when you already plan to call Destinations API in production and want Claude Code to stay aligned with the vendor’s canonical field names and lookup flows rather than hallucinating country or carrier tables.
- Official Claude plugin marketplace entry for TelecomsXChange Destinations API
- Global telecom database: MCC/MNC codes, mobile network operators, country coverage
- E.164 and E.212 mapping support for numbering and routing logic
- Carrier billing and destination metadata for telecom SaaS builders
- Single-plugin bundle focused on API-backed agent workflows
Telecomsxchangeapi Destinations Api Claude Plugin by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install telecomsxchangeapi-destinations-api-claude-plugin@TelecomsXChangeAPi/destinations-api-claude-pluginAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | October 12, 2025 |
| Repository | TelecomsXChangeAPi/destinations-api-claude-plugin ↗ |
What it does
Register the Destinations API Claude plugin when you are building telecom, routing, or billing features and need MCC/MNC, E.164, and E.212 data inside agent-assisted coding sessions.
Who is it for?
Best when you're creating SMS, voice, MVNO, or carrier-billing APIs and need structured telecom destination data while coding integrations.
Skip if: Typical web SaaS with no telephony stack, or developers who only need generic REST patterns without operator databases.
What you get
After install, your Claude Code sessions can ground integration code and API calls in Destinations API’s global operator and numbering identifiers.
- Registered Destinations API plugin in Claude Code
- Agent-grounded integration scaffolding for telecom lookups
- Consistent reference to MCC/MNC and E.164/E.212 fields in generated code
By the numbers
- pluginCount: 1
- repository: TelecomsXChangeAPi/destinations-api-claude-plugin
- official marketplace listing for Destinations API
Recommended Plugins
Abix5 Memory HindsightHindsight memory bank integration for Claude Code
Agentic Dev Io Mcp Code ExecutionToken-efficient MCP server interaction through code execution.1
Agneym Agneym Claude MarketplaceClaude Code plugin marketplace for Agney's plugins
Akkomar Mozdata Claude Plugin1 plugin
Amitpatole Claude Genkit PluginFirebase Genkit Plugin for Claude Code12
Aserper RtfdSpoonfeed your AI coding assistant with up to date documentation efficiently and without using a cloud service with the RTFD mcp server that runs on YOUR machine without any API key requirements!14How it compares
Official telecom API integration plugin, not a generic GitHub-issues skill or a code-review bundle.
FAQ
Who is Telecomsxchangeapi Destinations Api Claude Plugin for?
Developers shipping telecom, messaging, or billing products who use Claude Code while integrating the Destinations API.
When should I use Telecomsxchangeapi Destinations Api Claude Plugin?
Use it during Build when you implement lookups for countries, MCC/MNC pairs, E.164 numbers, or carrier billing destinations.
How do I add Telecomsxchangeapi Destinations Api Claude Plugin to my agent?
Add the TelecomsXChangeAPi/destinations-api-claude-plugin marketplace source in Claude Code and enable the plugin, then configure Destinations API credentials per vendor docs.