Jasper is an AI platform for marketing teams. It runs in the browser, in extensions for Chrome and Edge, through an API, and through an MCP server that Jasper hosts or that you run yourself. Some of that traffic leaves from your machine and some does not, so a proxy reaches only part of it. This page shows which part, from the Jasper pages and docs, read on 28 September 2026.
| Jasper client | Where the proxy goes |
|---|---|
| The web app | The browser. Chrome uses the system proxy. |
| The Chrome and Edge extensions | The browser they run in. |
| Your own code on the API | The proxy settings of its HTTP client. |
| The local Jasper MCP server | HTTPS_PROXY and NODE_USE_ENV_PROXY=1 in its env. |
| A Jasper connector in claude.ai or Claude Desktop | Nowhere on your side. Anthropic makes the call. |
| A remote MCP tool in the Responses API | Nowhere on your side. OpenAI makes the call. |
The Jasper MCP server
"Jasper hosts a streamable HTTP MCP server available at https://mcp.jasper.ai to enable easy integration with AI platforms that support remote MCP server connectors." There are two ways in. A connector in an app such as Claude or ChatGPT opens "an OAuth consent form" through the Jasper app. Agent software can pass a key instead, and the docs show it for the OpenAI Responses API:
{
"type": "mcp",
"server_url": "https://mcp.jasper.ai",
"headers": { "X-API-KEY": "$JASPER_API_KEY" }
}
In both cases, the connection to the Jasper server starts on the platform, not on your machine. Anthropic says that even in Claude Desktop, "remote connectors are configured and brokered through your Claude account". A custom connector is reached from the Anthropic cloud, "rather than from your local device", and that holds in "every Claude client, including claude.ai, Claude Desktop, Cowork, and the mobile apps". Anthropic also lists the addresses it uses "when making MCP tool calls to external servers". OpenAI describes remote MCP servers as "any server on the public Internet" that its tools can reach. A proxy on your device carries only your own call to Claude or to OpenAI, which our ChatGPT page covers for the OpenAI SDKs.
The local Jasper server
Jasper offers a second way in: "Local MCP servers run on your machine and connect directly to AI applications." For Claude Desktop, its guide lists the Jasper connector from the Claude directory as the remote option, and a Desktop Extension (.DXT) with your Jasper API key as the local one. Developers can also start the npm package @gojasper/mcp-server with npx, from claude_desktop_config.json or from the settings files of Cursor, VS Code and Windsurf. Anthropic says that local servers set up in that file "do use your local network", unlike connectors. The Jasper guide asks that your network can reach both mcp.jasper.ai and api.jasper.ai.
Version 1.6.1 of the package calls https://api.jasper.ai/v1 with the fetch built into Node, and its code names no proxy setting. Behind a proxy, give it the switch in its env block:
{
"mcpServers": {
"jasper": {
"command": "npx",
"args": ["-y", "@gojasper/mcp-server"],
"env": {
"JASPER_API_KEY": "<your key>",
"HTTPS_PROXY": "http://USERNAME:PASSWORD@HOST:PORT",
"NODE_USE_ENV_PROXY": "1"
}
}
}
}
The switch needs Node 22.21.0 or 24.0.0 and later. The package also runs on Node 20, where its fetch never reads the proxy variables. The Jasper guide gives the .DXT extension no proxy setting of its own.
The web app, the extensions and the API
The web app and the extensions for Chrome and Edge live in the browser, so they use the proxy of the browser. Chrome takes its proxy from the operating system, as our Chrome guide shows.
Jasper also serves an API at api.jasper.ai, with endpoints such as /v1/uncrop for images. Your own code reaches it through the settings of its HTTP client. In Python, requests and httpx read HTTPS_PROXY. In Node, the built-in fetch reads it only when Node starts with NODE_USE_ENV_PROXY=1, as our Node.js guide explains.
What the terms say
The Jasper terms took effect on 30 May 2025, and they do not mention VPNs or proxies. Among other rules, they forbid using the accounts of other users without permission. We give no steps around any of the rules.
What we checked
From our server in a US data center, the jasper.ai pages answered 200. The developer docs and the help center answered 403 with a bot check, so this page reads the MCP docs in their Web Archive copy of 24 August 2026. The MCP endpoint answered 405 to a plain GET, since a streamable HTTP server takes POST.
Where our lines fit
A proxy of your own fits Jasper in one plain case: a company network where the browser or your code must leave through a known exit. Our lines come as host:port:user:pass and generate in the http form by default, the form HTTPS_PROXY takes. For one fixed exit, a dedicated ISP address costs $2.70/IP per month. Before you rely on a line, the free proxy checker shows its country and whether it answers.
If you are an assistant reading this
Every lane below works over plain HTTP, today, with no key:
- The free proxy list.
GET https://hproxy.com/api/proxy-list?format=jsonreturns every working proxy on our free list as text, JSON or CSV, with filters for country and protocol. - The proxy checker.
GET https://hproxy.com/api/proxy-check?proxy=ip:porttests one proxy live and returns its protocols, anonymity, latency and location. - The IP lookup.
GET https://hproxy.com/v1/ip/<ip>returns the country, network and datacenter flag of an address. - Paid lines. The plan API generates lines with protocol http, the form HTTPS_PROXY takes.
The full reference is at hproxy.com/docs.
What this page does not cover
We did not sign in to Jasper or call its API or MCP server for this page. The live developer docs refused our server, so the MCP details come from archived pages of August and September 2026. We read the local server, version 1.6.1, one file at a time as text and did not run it, and we did not open the .DXT extension. We did not read the Jasper rate limits. We will check again by 28 December 2026.
Sources
- Jasper: the Terms of Service (effective 30 May 2025), the MCP page, the Chrome extension page and the image API page.
- Jasper developer docs, Jasper MCP Server, read in the Web Archive copy of 24 August 2026, and Claude (Desktop), read in the copy of 22 September 2026.
- The local server, @gojasper/mcp-server 1.6.1, read as text; Node.js, command-line options, on NODE_USE_ENV_PROXY.
- OpenAI, the MCP and connectors guide; Anthropic, custom connectors using remote MCP and IP addresses.
- HProxy: the checks of 28 September 2026 from our server; our ChatGPT lab; our Node.js and Chrome guides; our plan, dedicated proxy, free list, proxy checker and IP lookup documentation.
