@diegoaltoworks/localize-remote-mcp-server 1.1.0 → 1.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +2 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -6,13 +6,13 @@ Bridge any remote HTTP MCP server into Claude Desktop.
6
6
 
7
7
  Claude Desktop only supports MCP servers that run locally as commands (stdio transport). It cannot connect to remote MCP servers over HTTP. The two transports are fundamentally incompatible:
8
8
 
9
- ![The broken approach — Claude Desktop cannot connect directly to a remote HTTP/SSE MCP server](docs/mcp_broken_approach.svg)
9
+ ![The broken approach — Claude Desktop cannot connect directly to a remote HTTP/SSE MCP server](docs/mcp_broken_approach.png)
10
10
 
11
11
  ## The solution
12
12
 
13
13
  This package bridges the gap. You configure it in Claude Desktop's config file, Claude launches it automatically, and it translates between stdio and your remote server's HTTP endpoint. You never run this yourself — Claude does.
14
14
 
15
- ![The working solution — localize-remote-mcp-server acts as a local stdio bridge](docs/mcp_working_solution.svg)
15
+ ![The working solution — localize-remote-mcp-server acts as a local stdio bridge](docs/mcp_working_solution.png)
16
16
 
17
17
  ## Setup
18
18
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@diegoaltoworks/localize-remote-mcp-server",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "Proxy a remote HTTP MCP server to localhost",
5
5
  "bin": {
6
6
  "localize-remote-mcp-server": "./bin/cli.js"