FileSeen

com.fileseenPublished by fileseen.comOfficial publisherv1.2.0Updated Oct 25, 2026

Send files as tracked links from any AI agent and see who opened them, page by page.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

FileSeen lets an assistant send files as tracked links and report who opened them, page by page.

What you can do
FileSeen is a remote MCP server, also runnable locally via the npm package fileseen-mcp, that turns files into tracked links an assistant can send on your behalf. According to the registry description, it then reports engagement: who opened each link and which pages they viewed. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Use it when you want an assistant to share a document or file and then follow up with visibility into whether and how recipients engaged with it, rather than sending an untracked attachment.
Requirements
Either connect to the remote endpoint at mcp.fileseen.com or run the npm package fileseen-mcp locally with npx, which needs Node.js. Authentication is required: a bearer token supplied as the Authorization header, or the FILESEEN_API_KEY environment variable for the local package. The API key comes from the FileSeen dashboard under Settings, API keys. Network access is needed.
Before you install
The server requires a FileSeen API key, passed as FILESEEN_API_KEY or the Authorization bearer header; treat it as a secret and keep it out of shared configuration. Sending files creates tracked links and records recipient viewing activity, so recipients' page-by-page reading data is collected and visible to you. The manifest lists no tools, so confirm what the server can send or change before relying on it.

Installation

In SourceWeft

  1. Open FileSeen in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.fileseen%2Ffileseen/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fileseen": {
      "type": "http",
      "url": "https://mcp.fileseen.com/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

6

check_if_seen

Check whether a FileSeen link was opened: opened yes or no, how many times, first and last open, and reading time per page where the user's plan includes it. If an email image was added, it also gives 'Email opened (approximate)': a hint only, never proof the email was read. Checking never counts as an open.

Parametersidrequired

recent_activity

Recent activity on my links

Recent visits across all the user's links, newest first: when, which document, who (name or email when the reader gave it, otherwise 'Viewer N'), country, device, reading time and the pages read. Opens by the same visitor within 30 minutes count as one visit. Use it for 'what happened this week' or 'who opened anything today'. Reading this never counts as an open.

Parameterslimitsince

Version history

2
  1. v1.2.0LatestOct 24, 2026
  2. v1.1.0Oct 23, 2026

Score

65% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.