Name: Telecomsxchangeapi Destinations Api Claude Plugin
Author: TelecomsXChangeAPi

Telecomsxchangeapi Destinations Api Claude Plugin

telecomsxchangeapi-destinations-api-claude-plugin is a Claude Code plugin for the Build phase that connects agent-assisted development to the Destinations API global telecom MCC/MNC and numbering database.

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.

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin

/plugin install telecomsxchangeapi-destinations-api-claude-plugin@TelecomsXChangeAPi/destinations-api-claude-plugin

Add to Claude Use the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:TelecomsXChangeAPi/destinations-api-claude-plugin") and the paste-ready config with skillselion.get_install_config("plugin:TelecomsXChangeAPi/destinations-api-claude-plugin").

About

What it does

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. Solo builders 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.

Highlights

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

Why builders use it

Building telecom routing or billing features without authoritative MCC/MNC and E.164 data forces manual lookups and risky hard-coded carrier tables.

After install, your Claude Code sessions can ground integration code and API calls in Destinations API’s global operator and numbering identifiers.

At a glance

Type - Plugin in LLM Integration.
Adoption - 0 installs, 1 stars, 0 votes.

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.