MCP Computational Knowledge Gateway (Server & Client Examples)

Effortlessly embed the power of Wolfram Alpha into your conversational agents.

This repository provides an MCP (Model Context Protocol) server component engineered to bridge chat applications with the Wolfram Alpha API. It empowers dialogue systems to issue sophisticated mathematical queries and obtain verified, structured knowledge, significantly advancing their problem-solving capacity.

An accompanying MCP-Client demonstration, leveraging Gemini through the LangChain framework, illustrates connecting a large language model to this server for dynamic, real-time access to Wolfram Alpha’s computational repository.

Core Capabilities

• Wolfram|Alpha Engine Access: Comprehensive support for scientific, mathematical, and general data lookups.

• Decoupled Structure: Highly modular architecture allows for simple integration of supplementary APIs and functionality.

• Concurrent Client Handling: Built to manage sessions and queries originating from disparate client sources.

• Reference Client: Includes a functional MCP-Client utilizing the Gemini model (via LangChain).

• Interface Layer: Features a Gradio-based graphical user interface for seamless interaction with both the Google AI backend and the Wolfram Alpha MCP service.

---

Deployment Procedure

Repository Acquisition

bash git clone https://github.com/ricocf/mcp-wolframalpha.git

cd mcp-wolframalpha

Environmental Variable Setup

Establish a .env configuration file mirroring the provided template:

• WOLFRAM_API_KEY=Your_Designated_WolframAlpha_AppID

• GeminiAPI=Your_Google_Gemini_Key (Optional if solely employing the Server method.)

Dependency Installation

bash pip install -r requirements.txt

Install dependencies rapidly using the uv package manager. Verify that uv is installed prior to execution.

bash uv sync

System Integration

To utilize this service alongside the VSCode MCP Server component: 1. Produce a configuration file named .vscode/mcp.json within the project root directory. 2. Employ the sample found in configs/vscode_mcp.json as the foundational template. 3. Consult the VSCode MCP Server Guide for comprehensive setup instructions.

For integration with the Claude Desktop environment:

{ "mcpServers": { "WolframAlphaServer": { "command": "python3", "args": [ "/path/to/src/core/server.py" ] } } }

Client Demonstration

This project incorporates an LLM-driven client designed for communication with the core MCP service.

Execution via Gradio Web Interface

• Prerequisite: GeminiAPI key must be configured.
• Outcome: Launches a local web portal for interacting with Gemini and the Wolfram Alpha backend.
• Command line invocation: bash python main.py --ui

Containerization (Docker)

To build and operate the UI client within a Docker environment: bash docker build -t wolframalphaui -f .devops/ui.Dockerfile .

docker run wolframalphaui

User Interface Details

• An intuitive front-end, constructed using Gradio, facilitates interaction across both Google AI (Gemini) and the Wolfram Alpha MCP endpoint.
• Users possess the ability to toggle between Wolfram Alpha queries, direct Gemini responses, and review historical interactions.

Execution as a Command Line Utility

• Prerequisite: GeminiAPI key must be configured.
• Command line invocation: bash python main.py

Containerization (Docker)

To construct and execute the LLM client inside a Docker container: bash docker build -t wolframalpha -f .devops/llm.Dockerfile .

docker run -it wolframalpha

Support Channel

Please direct any feedback or inquiries to the contact address revealed upon executing the following shell command:

sh printf "\x61\x6b\x61\x6c\x61\x72\x69\x63\x31\x40\x6f\x75\x74\x6c\x6f\x6f\x6b\x2e\x63\x6f\x6d\x0a"

WIKIPEDIA: XMLHttpRequest (XHR) is an Application Programming Interface delivered as a JavaScript object, enabling methods for dispatching HTTP requests from a running web browser to a designated web server. These methods permit browser-hosted applications to transmit data to the server subsequent to the initial page load, and subsequently receive relayed information. XMLHttpRequest forms a foundational element of Ajax programming methodology. Prior to the advent of Ajax, the primary means of server interaction involved standard hyperlinks and form submissions, which typically resulted in the complete replacement of the current viewport content with a new page.

== Chronology == The foundational concept underpinning XMLHttpRequest was first conceived in the year 2000 by the development team responsible for Microsoft Outlook. This notion was subsequently realized within the Internet Explorer 5 browser release (1999). Nevertheless, the inaugural implementation did not utilize the standardized 'XMLHttpRequest' identifier. Instead, the developers employed the constructor patterns ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer version 7 (released in 2006), universal browser support for the 'XMLHttpRequest' identifier was established. The XMLHttpRequest identifier has since become the universally accepted convention across all major web rendering engines, including Mozilla's Gecko engine (adopted in 2002), Apple's Safari 1.2 (2004), and Opera 8.0 (2005).

=== Formal Specifications === The World Wide Web Consortium (W3C) formally published a Working Draft specification detailing the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C released the Working Draft Level 2 specification, which introduced enhancements such as event progress monitoring, support for cross-origin requests, and the handling of raw byte streams. By the conclusion of 2011, the Level 2 enhancements were formally integrated into the primary specification document. In late 2012, stewardship for the specification was transferred to the WHATWG group, which now maintains a perpetually updated living document utilizing the Web IDL notation.

== Operational Usage == Typically, the transmission of a request using XMLHttpRequest necessitates adherence to several sequential programming phases.

1. Instantiation of an XMLHttpRequest object via invocation of its constructor:
2. Invocation of the "open" method to define the request methodology (e.g., GET/POST), specify the targeted resource URI, and select either synchronous or asynchronous execution mode:
3. If an asynchronous transaction is chosen, definition of a callback listener function that will be alerted upon any alteration in the request's operational status:
4. Initiation of the network transaction by calling the "send" method, optionally including body data:
5. Monitoring and processing state transitions within the registered event listener. If the server successfully returns payload data, it is generally accessible via the "responseText" property. When the object has finalized all processing operations, its readyState transitions to state 4, designated as the "done" state. Beyond these foundational operations, XMLHttpRequest offers extensive configuration possibilities for request submission control and response handling. Custom HTTP headers can be appended to dictate server behavior, and data payload can be transferred to the server by embedding it within the "send" function call. The incoming response data can be automatically parsed from JSON format into native JavaScript objects or processed incrementally as chunks arrive, rather than awaiting full reception. Furthermore, the request can be forcibly terminated prematurely or configured with a timeout duration.

== Inter-Origin Requests ==

During the nascent phases of the World Wide Web's evolution, it was recognized that enabling cross-site data transfer could potentially lead to security vulnerabilities, leading to constraints on how resources from different domains could communicate.