pshare-share-mcp

MCP server that allows any AI (Claude Code, Claude Desktop, or other MCP clients) to upload files/folders to Pshare and get back a share link — exactly like the manual flow: upload via the UI then click the Share button to copy the link.

No login or token needed — consistent with Pshare's current architecture (the web client itself doesn't really authenticate, it just uses a self-generated X-Browser-Id).

Requirement: you already have a running Pshare instance somewhere (localhost or on the LAN) — this repo is only an MCP server that calls Pshare's REST API, it doesn't run Pshare itself.

Provided tools

pshare_upload

Returned result: a share link of the form http://<pshare-host>/?share=<N> along with the file count and password status.

Files larger than 90MB automatically switch to chunked upload (same as the web client's LAN upload behavior); no further action needed.

Related MCP server: SharePoint MCP Server

Installation

Just clone this repo — no need to download Pshare itself:

git clone https://github.com/ntanhprt/Pshare-mcp.git
cd Pshare-mcp
pnpm install
pnpm build      # biên dịch ra dist/

Configuration (environment variables)

localhost is only correct when the MCP server runs on the very machine running Pshare. localhost always points to "the machine running that process" — so if you install this MCP on a different machine/laptop than the one running Pshare (even on the same LAN), you must change it to the real IP of the machine running Pshare. For example, if Pshare is running on a machine with IP 192.168.3.7:

PSHARE_BASE_URL=http://192.168.3.7:5173 claude mcp add pshare-share -- node "$(pwd)/dist/index.js"

Only keep the default localhost when you run the MCP (stdio) directly on the same machine running Pshare.

Standalone test run

# stdio (mặc định)
pnpm start

# HTTP/SSE — AI ở máy khác trong LAN cũng gọi được
pnpm start:http
# → nghe tại http://<PSHARE_MCP_HOST>:<PSHARE_MCP_PORT>/mcp

Integration guide for other developers

1. Use with Claude Code (stdio transport — recommended when the AI runs on the same machine/host as Pshare)

After cloning + building (see Installation above), from inside the Pshare-mcp directory:

claude mcp add pshare-share -- node "$(pwd)/dist/index.js"

To point to Pshare on another machine, pass env via -e (see the localhost note in Configuration):

claude mcp add pshare-share \
  -e PSHARE_BASE_URL=http://192.168.3.7:5173 \
  -- node "$(pwd)/dist/index.js"

Verify it's registered:

claude mcp list

2. Use with Claude Desktop (stdio transport)

Open the config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows) and add:

{
  "mcpServers": {
    "pshare-share": {
      "command": "node",
      "args": ["/đường/dẫn/tuyệt/đối/tới/Pshare-mcp/dist/index.js"],
      "env": {
        "PSHARE_BASE_URL": "http://localhost:5173"
      }
    }
  }
}

Restart Claude Desktop to get the pshare_upload tool.

3. Use over HTTP/SSE (when the AI runs on another machine on the same LAN)

Run the MCP server on the machine hosting Pshare (or any machine that can reach Pshare):

PSHARE_BASE_URL=http://localhost:5173 pnpm start:http

On the client machine (Claude Code, or any MCP client that supports HTTP transport), point to:

http://<IP-máy-chạy-mcp>:7317/mcp

Example with Claude Code:

claude mcp add --transport http pshare-share http://192.168.3.7:7317/mcp

4. Use with any other AI/agent framework

MCP is a standard JSON-RPC protocol — any MCP client (LangChain MCP adapter, custom agent, etc.) can connect, just need:

• stdio: spawn the command node dist/index.js and communicate via stdin/stdout.

• HTTP: call POST http://<host>:<port>/mcp following MCP's Streamable HTTP transport spec.

Security notes

This MCP server does not authenticate — anyone who can reach it (via stdio if they can run the process, or via HTTP if they can access the host:port) can upload/share files to the real Pshare. This is consistent with Pshare itself (no auth on the upload/share API), but keep this in mind when exposing the HTTP transport beyond the LAN.