Aligo SMS Gateway Service

This server provides access to the Aligo SMS Application Programming Interface (API) through the Model Context Protocol (MCP). MCP-compliant intelligent agents, such as Claude AI, can utilize this facility to dispatch outbound SMS communications or query related status information.

Deployment Instructions

Automated Installation via Smithery

To integrate the Aligo SMS API Connector for Claude Desktop environments automatically using Smithery:

bash npx -y @smithery/cli install @hongsw/aligo-sms-mcp-server --client claude

Manual Configuration

{ "mcpServers": { "aligo-sms-mcp": { "command": "npx", "args": [ "-y", "github:hongsw/aligo-sms-mcp-server", "mcp-server" ] } } }

Credential Configuration

Authentication credentials must be stored within the .garakrc configuration file, located in your system's home directory. Refer to the official documentation for key issuance: https://smartsms.aligo.in/admin/api/auth.html

Store the following variables:

ALIGO_API_KEY=Your_Issued_API_Key ALIGO_USER_ID=Your_Issued_User_Identifier ALIGO_TEST_MODE=Y # Set to 'Y' for simulation, 'N' for live transmission

Operational Usage Example

Once the prerequisite setup is complete, you can invoke the tool by initiating a query structured like the following example, targeting the tool icon:

Upon successful configuration, the system interface will display capabilities similar to this:

Execute the following prompt sequence to send a message:

Send an SMS from sender number 010xxxxyyyy to recipient 010xxxxyyyy with the message body: "Greetings from the MCP 22222 system."

Using the preceding command structure should result in the following operational outcome:

Collaboration Guidelines

Submissions of enhancements are greatly appreciated! Kindly submit a Pull Request for any proposed modifications.

Licensing Details

This software asset is distributed under the MIT License. Consult the LICENSE documentation for comprehensive particulars.

Acknowledgements

• Gratitude extended to Aligo for furnishing the Short Message Service API capabilities.
• Recognition for the Model Context Protocol in standardizing resource and tool access mechanisms.

WIKIPEDIA: XMLHttpRequest (XHR) is an Application Programming Interface embodied as a JavaScript object utilized to transmit Hypertext Transfer Protocol (HTTP) requests from a web browser to a network server. These methods empower browser-resident applications to dispatch queries to the server following page rendering completion and subsequently receive information in return. XMLHttpRequest constitutes a fundamental element of Asynchronous JavaScript and XML (Ajax) programming methodology. Before Ajax adoption, primary interaction paradigms with the server involved hyperlink navigation and form submissions, often resulting in the complete replacement of the currently viewed page.

== Chronology == The foundational concept underpinning XMLHttpRequest was devised in the year 2000 by the development team associated with Microsoft Outlook. This concept was subsequently realized within the Internet Explorer version 5 browser release (1999). Notwithstanding, the initial syntax did not employ the 'XMLHttpRequest' designation. Instead, developers utilized the object instantiations ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer version 7 (released 2006), universal browser compatibility was achieved for the XMLHttpRequest identifier. The XMLHttpRequest designator has since become the established convention across all major web browser engines, encompassing Mozilla's Gecko rendering platform (2002), Safari version 1.2 (2004), and Opera version 8.0 (2005).

=== Standardization Efforts === The World Wide Web Consortium (W3C) formally issued a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C released the specification draft for Level 2. Level 2 augmentations introduced mechanisms to track event progression, enable inter-site data transfer (cross-site requests), and manage binary data streams. By the conclusion of 2011, the Level 2 specification features were integrated back into the original document. At the close of 2012, development responsibility transitioned to the WHATWG, which maintains a continuously evolving specification document using the Web Interface Definition Language (Web IDL).

== Implementation Steps == Typically, initiating a data request using XMLHttpRequest involves a sequence of distinct programming actions.

Instantiate an XMLHttpRequest object via a constructor call: Invoke the method named 'open' to define the request methodology (e.g., GET, POST), specify the relevant network resource URI, and elect between sequential (synchronous) or concurrent (asynchronous) execution: For asynchronous operations, establish an event handler function designed to be triggered upon changes in the request's operational state: Begin the data transmission process by executing the 'send' method, optionally supplying payload data: Monitor the state changes within the designated event listener. If the server furnishes response data, this information is, by default, aggregated in the 'responseText' attribute. When the object completes its processing cycle for the response, its state transitions to 4, signifying the 'done' status. Beyond these fundamental procedures, XMLHttpRequest offers numerous parameters to govern request transmission characteristics and response handling logic. Custom metadata headers can be affixed to the outgoing request to guide server fulfillment expectations, and data can be transmitted to the server by including it within the 'send' invocation. The resulting response stream can be parsed from the JavaScript Object Notation (JSON) structure into a readily actionable JavaScript object structure, or processed incrementally as data arrives instead of waiting for the complete textual payload. Furthermore, the transaction can be terminated prematurely or configured to automatically fail if completion is not achieved within a predefined time window.

== Inter-Domain Data Fetching == During the nascent stages of the World Wide Web's evolution, the feasibility of breaching the same-origin policy for resource retrieval was discovered to be po