ProjectSend MCP

The ProjectSend MCP server enables AI assistants to manage file sharing operations within a ProjectSend Cloud account. It allows agents to save files, generate private links, track downloads, and on paid plans, organize folders and manage client accounts. The connection is established via OAuth-like approval without requiring API keys, ensuring users retain full control and can disconnect at any time.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-18Operated by ProjectSend

MCP endpoint (Streamable HTTP)

https://files.projectsend.site/mcp

Vendor documentation

What you can do with it

Save AI-generated reports or summaries as files and retrieve private sharing links
Upload files from scripts or sandboxes and get shareable URLs
Track who downloaded specific files and when
Organize files into folders and create client accounts on Pro/Business plans

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http projectsend-mcp https://files.projectsend.site/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add projectsend-mcp --url https://files.projectsend.site/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable projectsend-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "projectsend-mcp": {
      "url": "https://files.projectsend.site/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "projectsend-mcp": {
      "type": "streamableHttp",
      "url": "https://files.projectsend.site/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start projectsend-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "projectsend-mcp": {
      "type": "http",
      "url": "https://files.projectsend.site/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http projectsend-mcp https://files.projectsend.site/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "projectsend-mcp": {
      "url": "https://files.projectsend.site/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "projectsend-mcp": {
      "serverUrl": "https://files.projectsend.site/mcp"
    }
  }
}

See all 2,329

Do you run ProjectSend MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing