Nuxt Backend for Model Context Protocol (MCP)

This repository presents a minimal Nuxt project configured to host an MCP backend instance, adhering to the Streamable HTTP Server Transport Specification.

Modify the contents of server/routes/mcp.ts to define your specific set of accessible tools, structured prompts, and requisite external resources, guided by the specifications in the mcp-handler repository.

The active MCP service endpoint will be accessible at the path /mcp.

Prerequisites & Setup

Ensure all necessary package dependencies are installed using:

bash pnpm install

Local Development

To initiate the development server, which typically runs on http://localhost:3000, execute the following command in a separate terminal session:

bash pnpm dev

Building for Production

Compile the application assets for a production release:

bash pnpm build

To locally verify the production output before deployment:

bash pnpm preview

Refer to the official Nuxt deployment guide for comprehensive deployment strategies.

Vercel Deployment Notes

For optimal performance, particularly when handling continuous data streams, confirm that Fluid compute is enabled for this function execution context.

Example Client Interaction

A utility script, script/test-client.mjs, is provided to facilitate quick testing of invocation endpoints.

Execute it referencing your local server address:

sh node scripts/test-client.mjs http://localhost:3000

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea