Apdf — PDF Tracking & Analytics

io.apdfPublished by apdf.ioOfficial publisherv1.1.1Updated Oct 24, 2026

PDF engagement layer for apps and agents: tracking links, read analytics, and a full PDF toolset.

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

A remote PDF engagement service that lets an assistant create tracking links, read PDF analytics, and work with PDF files.

What you can do
Apdf is a hosted PDF engagement layer for apps and agents. According to its registry description, it provides tracking links, read analytics, and a full PDF toolset. The manifest does not list individual tools, so the exact operations available through the MCP endpoint are not documented here.
When to use it
Consider it when an assistant needs to distribute PDFs with trackable links or report on how recipients engage with those documents. It is less relevant if you only need local PDF editing with no analytics.
Requirements
A remote MCP endpoint at over streamable HTTP. OAuth authentication is required. No environment variables, headers, or packages are declared.
Before you install
Installing grants the assistant access to your Apdf account through OAuth, including any documents and analytics data held there. Tracking links and read analytics collect information about recipients, so consider privacy and consent before using them. The manifest lists no tools, so review the actual permissions requested during OAuth.

Installation

In SourceWeft

  1. Open Apdf — PDF Tracking & Analytics in the dashboard and add it to a workspace.
  2. Connect the required 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/io.apdf%2Fmain/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "apdf-pdf-tracking-analytics": {
      "type": "http",
      "url": "https://apdf.io/mcp/main"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

67% 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

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.