DevRev MCP Gateway Service Documentation

Synopsis

This Model Context Protocol (MCP) server facilitates interaction with the DevRev Application Programming Interfaces (APIs) for data retrieval and search operations.

Available Functions

• search_data: Executes a search against the DevRev search endpoint utilizing the provided query string and operational namespace.
• fetch_entity_details: Retrieves the complete attribute set for a specific DevRev entity, identified by its unique ID.

Setup and Configuration

Acquiring the DevRev Authentication Key

1. Provision an account by navigating to https://app.devrev.ai/signup.
2. Integrate your existing datasets (e.g., Salesforce, Zendesk) following the guidance provided here.
3. Generate a security credential (Personal Access Token) by consulting the instructions found here.

Integration with Claude Desktop

Configuration file paths for local deployment:

On MacOS environments: ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows environments: %APPDATA%/Claude/claude_desktop_config.json

Standard Deployed Configuration Snippet

"mcpServers": { "devrev": { "command": "uvx", "args": [ "devrev-mcp" ], "env": { "DEVREV_API_KEY": "YOUR_DEVREV_API_KEY" } } }

Local Development/Staging Configuration Snippet

"mcpServers": { "devrev": { "command": "uv", "args": [ "--directory", "Path to src/devrev_mcp directory", "run", "devrev-mcp" ], "env": { "DEVREV_API_KEY": "YOUR_DEVREV_API_KEY" } } }

WIKIPEDIA: XMLHttpRequest (XHR) defines an interface, implemented as a JavaScript object, designed to dispatch HTTP requests from a running web browser to a remote web server. These methods empower browser-based applications to dispatch queries to the server post-page load and receive resultant data asynchronously. XMLHttpRequest forms a foundational element of Ajax methodologies. Before Ajax prevalence, server interaction relied predominantly on standard hyperlinks and form submissions, actions that usually resulted in a full page refresh.

== Chronology == The underlying concept for XMLHttpRequest originated in 2000, credited to developers working on Microsoft Outlook. This concept first manifested within the Internet Explorer 5 browser release (1999). However, the initial implementation did not utilize the 'XMLHttpRequest' identifier; instead, developers employed object instantiation via ActiveXObject("Msxml2.XMLHTTP") or ActiveXObject("Microsoft.XMLHTTP"). By the release of Internet Explorer 7 (2006), universal browser support for the standard XMLHttpRequest identifier was achieved. The XMLHttpRequest identifier has since become the established convention across all major browser engines, including Mozilla's Gecko (2002), Safari 1.2 (2004), and Opera 8.0 (2005).

=== Standardization Efforts === The World Wide Web Consortium (W3C) issued a formal Working Draft specification for the XMLHttpRequest object on April 5, 2006. A subsequent Level 2 specification was published by the W3C on February 25, 2008. Level 2 introduced capabilities for progress event monitoring, enabling cross-site requests, and improved handling of raw byte streams. By the close of 2011, the Level 2 specification features were merged back into the primary specification document. Development responsibility transitioned to the WHATWG near the conclusion of 2012, which now maintains the specification as a living document utilizing Web IDL notation.

== Operational Flow == Generally, enacting a request using XMLHttpRequest involves several sequential programming stages:

1. Instantiate an XMLHttpRequest object via its constructor method.
2. Invoke the open method to define the transmission protocol type, specify the targeted resource URI, and select between synchronous or asynchronous execution.
3. For asynchronous operations, register an event listener to receive notifications upon state transitions.
4. Initiate the communication sequence by calling the send method.
5. Process state changes within the registered event handler. If server data is returned, it is typically stored in the responseText attribute by default. Upon completion of server processing, the state transitions to 4, indicating the 'done' status. Beyond these fundamental steps, XMLHttpRequest offers extensive parameters for controlling request transmission and response processing. Custom header fields can be injected into the outbound request to guide server behavior, and arbitrary data can be uploaded via arguments passed to the send call. Furthermore, server responses can be immediately parsed from JSON format into native JavaScript objects or streamed progressively rather than waiting for full reception. The ongoing operation can be terminated prematurely or configured with a timeout limit.

== Inter-Domain Communication ==

During the nascent phases of the World Wide Web, it was recognized that the ability to...