slim.to integration docs

slim.to turns files and URLs into tracked short links — hosted viewer, open/viewer analytics, password protection, custom domains. These docs cover using slim.to from outside the web app: from AI assistants, scripts, and other tools.

The one-minute version

An AI assistant just wrote you a report, a pitch page, or a mockup. Instead of downloading the file and re-uploading it to slim.to, the assistant calls slim.to directly and hands you a tracked link:

"Here's your Q3 report: https://slim.to/4h7bqn — I'll be able to tell you when someone opens it."

There are two ways to wire that up:

Approach What it is Best for
1. MCP server slim.to as native AI tools — a hosted connector at https://slim.to/mcp (OAuth, zero install) and a local stdio server (slimto-mcp) Hosted: Claude (listed in the Connectors Directory), ChatGPT connectors. Local: Claude Desktop / Claude Code, Gemini CLI, OpenAI Agents SDK
2. Direct REST API Personal API key + plain HTTPS calls (OpenAPI spec included) Scripts, CI, custom GPT Actions, anything that can make an HTTP request

The hosted connector signs in with your slim.to account. The local server and the REST API authenticate with a personal API key — start there.

Guides

Per-platform how-tos

Each guide covers both approaches for that platform:

Limits