# Veilfile MCP server

> Host private files for AI agents behind unguessable links that expire on a schedule

- Listing: https://mcp.tc/i/veilfile
- Connect: use the server's own URL `https://veilfile.com/mcp/` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Utilities](https://mcp.tc/c/utilities)
- Vendor: Veilfile
- Homepage: <https://veilfile.com/>

## About

Veilfile hosts private artifacts for AI agents. Agents upload files through the MCP server or a REST API, and each file gets an unguessable link that expires on schedule.

The hosted endpoint is https://veilfile.com/mcp (Streamable HTTP). Add it to an agent as a remote MCP server and sign in when the agent asks. A CLI is also available through npm or pip, started with veilfile login.

## What it can do

- Upload files for AI agents to a private store
- Share files through unguessable links
- Links expire on a set schedule

## Tools (4)

- `upload_artifact`: Upload a file from base64 content and return its id, its private share link as url, expires\_at, size\_bytes and secret\_flags.
- `create_upload_url`: Create a one-time upload URL for a file too large to send as base64 through upload\_artifact.
- `list_artifacts`: List the files in this workspace, newest first. (read-only)
- `revoke_artifact`: Revoke a file by its id. (can modify or delete data)

## Example prompts

- "Upload this report to Veilfile and give me a link that expires in 24 hours"
- "Host this screenshot privately and share the link"
- "Store the generated build artifact as a temporary private file"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http veilfile https://veilfile.com/mcp/
```

2. Start Claude Code, type `/mcp`, pick **veilfile** and choose **Authenticate**. A browser window opens for the Veilfile sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Veilfile** and paste this URL:

```url
https://veilfile.com/mcp/
```

3. Click **Add**, then **Connect**, and sign in when Veilfile asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Veilfile&connectorUrl=https%3A%2F%2Fveilfile.com%2Fmcp%2F>) (opens connector settings)

2. Check that the URL reads `https://veilfile.com/mcp/` and click **Add**.

3. Click **Connect** and sign in when Veilfile asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://veilfile.com/mcp/` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Veilfile to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=veilfile&config=eyJ1cmwiOiJodHRwczovL3ZlaWxmaWxlLmNvbS9tY3AvIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "veilfile": {
      "url": "https://veilfile.com/mcp/"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=veilfile&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fveilfile.com%2Fmcp%2F%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"veilfile","type":"http","url":"https://veilfile.com/mcp/"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "veilfile": {
      "type": "http",
      "url": "https://veilfile.com/mcp/"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "veilfile": {
      "serverUrl": "https://veilfile.com/mcp/"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add veilfile --url https://veilfile.com/mcp/
codex mcp login veilfile
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.veilfile]
url = "https://veilfile.com/mcp/"
```

### Gemini CLI

```bash
gemini mcp add --transport http veilfile https://veilfile.com/mcp/
```

Then, inside Gemini CLI, run `/mcp auth veilfile` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "veilfile": {
      "type": "http",
      "url": "https://veilfile.com/mcp/"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://veilfile.com/mcp/`.

## Recent changes

- 2026-11-10 14:48 UTC: New version 1.0.1 (was 0.1.0), reported by the server. Source: automatic check.
- 2026-11-09 23:25 UTC: Tracking started: 4 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/veilfile#history (Atom feed: https://mcp.tc/i/veilfile/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.1
- MCP protocol version: 2025-06-18
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-09
- Updated: 2026-11-09

---
Source: https://mcp.tc/i/veilfile (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
