Using slim.to with Claude
Two ways to let Claude create slim.to links from the artifacts and files it produces: the MCP server (best — native tools) or the REST API (no setup beyond an API key).
The hosted connector only needs a slim.to account. The local server and the REST API also need a personal API key.
Approach 1 — MCP server
Claude Code (CLI)
Signed in to Claude Code with a claude.ai account? Connect slim.to from its
Connectors Directory listing
and it is already available — it shows up in /mcp. The local server here is
for uploading files from your disk by path, or for API-key setups.
One command:
claude mcp add slimto \
--env SLIMTO_API_KEY=slim_your_key_here \
-- uvx --from /path/to/slimto/mcp slimto-mcp
Then in any session:
You: Write up the Q3 numbers as a PDF and give me a slim.to link for it.
Claude: (writes the PDF, calls
create_link_from_file) Done — https://slim.to/4h7bqn. I can check who's opened it whenever you ask.
Scope the server to one project with claude mcp add --scope project …
(writes .mcp.json in the repo) or make it available everywhere with
--scope user.
Claude Desktop
The quickest route is the hosted connector: connect it once from its Connectors Directory listing and it is in Claude Desktop too. Use the local server when you want Claude to upload files from your disk by path.
Add the server to claude_desktop_config.json
(Settings → Developer → Edit Config):
{
"mcpServers": {
"slimto": {
"command": "uvx",
"args": ["--from", "/path/to/slimto/mcp", "slimto-mcp"],
"env": {
"SLIMTO_API_KEY": "slim_your_key_here"
}
}
}
}
Restart Claude Desktop; the slimto tools appear under the tools icon. Because the server runs on your machine, Claude Desktop can upload any local file it can see — including files it just created.
claude.ai, Desktop and mobile — from the Connectors Directory
slim.to is listed in Claude's Connectors Directory, so no install is needed:
- Open the slim.to listing and click Connect — or search for "slim.to" under Customize → Connectors.
- Claude opens the slim.to sign-in/consent page — click Authorize.
Connect once on claude.ai and slim.to is also there in Claude Desktop, the mobile apps, and Claude Code when it is signed in with the same claude.ai account.
Team and Enterprise plans: an Owner adds slim.to for the organization from Organization settings → Connectors, then each member connects with their own slim.to account. Members without that permission see a Request button, which notifies the Owners.
Adding by URL. Add custom connector with the URL https://slim.to/mcp
still works, but Claude then lists it as a Custom connector instead of the
directory one. Prefer the listing.
That's it. Claude on web and mobile can now shorten URLs, publish the HTML
pages it writes as tracked links (create_link_from_content), update an
already-shared link in place (replace_link_content — same URL, analytics
intact), delete links, list your links, and answer "did anyone open it?" from
your analytics. Revoke access anytime from Dashboard → Settings → Connected
apps.
Large files. Content sent inline has to be generated token-by-token by Claude, which is slow for big files and can be cut short by tool-call size limits. slim.to handles this three ways:
source_url— slim.to downloads the content itself. By far the fastest path, but the URL must be publicly readable; slim.to fetches it as an anonymous visitor, so private links won't work.- Chunked upload (
start_content_upload) — for content Claude is writing itself. This guarantees the file arrives whole; it does not make it quicker, since Claude still has to write every byte. sha256/expected_bytes— an integrity check, so a truncated upload is rejected instead of published broken. Only pass values computed with a code tool; a guessed digest will always fail the check.
Note the remote server's upload tool takes content rather than a file path (hosted Claude has no access to your disk) — for uploading arbitrary local files, Claude Desktop/Code with the local server is the better fit.
Several pages in one go
Nothing limits a prompt to one link. A launch with a page per channel, a landing page per audience, or an A/B pair of headlines is the same flow repeated, and Claude will happily do the repeating:
You: Write a landing page for each of these audiences — sales, recruiting, project managers — leading with the features each one cares about. Publish them on slim.to at
/for-<audience>, tag them allaudience-pages, and give each call-to-action button its own tracked short link to https://example.com/signup so we can compare click-through.Claude: (calls
create_short_linkthree times, thencreate_link_from_contentthree times) Done — slim.to/for-sales, slim.to/for-recruiting and slim.to/for-project-managers, each with ajoin-<audience>button link.
Conventions that make the batch easy to live with:
- Slugs as a family —
for-sales/join-sales, so a search forfor-orjoin-returns the whole set. - A tag on every link —
tagsis accepted bycreate_link_from_content,create_short_linkandfinish_content_upload, andlist_linksfilters by it, so "list the audience-pages links" works months later. - A short link per call to action — the page's own analytics report reads (viewers, time on page, scroll depth); the short link reports clicks. The ratio is your conversion rate per variant, with no extra tooling.
- Compare by asking — "Which of the audience pages is doing best?" has
Claude call
get_link_analyticsonce per link and summarise. Then "rewrite the weakest one and publish it to the same link" usesreplace_link_content, so the URL and its history survive the rewrite.
Mind the plan: the free tier caps active links at five, and a page plus a button is two links per variant. A batch like the one above needs Pro.
The worked example, with real pages, is in One prompt, six landing pages.
Approach 2 — REST API (no MCP)
Claude Code can drive the API with plain curl — handy when you don't want to
install anything. Put the key in your shell env (~/.zshrc):
export SLIMTO_API_KEY=slim_your_key_here
Then ask Claude Code:
Upload
./report.pdfto slim.to and give me the short link. UsePOST https://slim.to/api/v1/fileswith theX-API-Keyheader from$SLIMTO_API_KEY, sending the file as multipart fieldfile.
Or teach it once by adding a note to your project's CLAUDE.md:
## Sharing deliverables
When I ask for a shareable link for a file, upload it to slim.to:
`curl -s -X POST https://slim.to/api/v1/files -H "X-API-Key: $SLIMTO_API_KEY" -F "file=@<path>" -F "title=<title>"`
and give me the `link.short_url` from the response.
The full endpoint reference is in the API quickstart.
Which approach?
| Local MCP (stdio) | Hosted MCP connector | REST | |
|---|---|---|---|
| Setup | one-time config | click Connect in the directory, then Authorize | just an env var |
| Claude discovers tools by itself | ✅ | ✅ | needs prompting / CLAUDE.md |
| Works on claude.ai web + mobile | ❌ | ✅ | ❌ (no shell) |
| Upload arbitrary local files | ✅ file path | content only | ✅ |
| Analytics queries ("who opened it?") | ✅ | ✅ | manual curl |
Use MCP where you can; REST is the universal fallback.