Introducing Sniptide, the pastebin for your agents

Sniptide is a pastebin built for how developers share code today. Paste a snippet or a whole folder, send a link you control, and find it again months later. Your coding agents can search and reuse the same library over MCP.

Most pastebins haven't changed in a decade. You get one file, a random link, ads, and no way to find what you pasted last month. So the code worth keeping ends up scattered across chat threads and old gists: the retry helper, the auth setup, the button your team agreed on. When a colleague asks for it, you go digging. When your agent needs it, the agent writes it again from scratch, a little different each time.

What you can do with Sniptide

• Share code with a link you control. A paste holds up to 10 files, or a whole folder, under a short or custom link. Make it private, unlisted or public, add a password, let it expire, let it burn after the first read, or invite people to view or edit.
• Find it again. Collections, stars and ⌘K search keep your snippets in reach, and every edit records a revision you can compare and restore.
• Keep patterns your agent can find. Coding agents search and read your snippets over MCP, and the CLI installs a collection as a skill.
• Hand off a project's .env. Env groups store a project's variables encrypted, sync with sniptide env, and share through a password link that expires.
• See what happened to a link. Each paste counts views, copies and referrers, without cookies.
• Post it anywhere. Links unfurl with a code preview, post straight to Slack or Discord, embed on a page or print as a PDF.

One pattern, from paste to agent

Say your team keeps a retry helper and a debounce hook it reuses everywhere. Here is how they become something your agent works from.

1. Save them as pastes

   Paste each file into a new paste. The editor sets the language from the file name and warns you when the code looks like a key.

2. File them in a collection

   Add both pastes to a collection called snippets. Its slug is the name the CLI and agents use.

3. Connect your agent

   Add the MCP server to Claude Code, then type /mcp, choose sniptide and pick Authenticate to sign in through the browser.

   claude mcp add --transport http sniptide https://app.sniptide.com/api/mcp

4. Ask for it

   Ask in plain language, such as "Use the retry helper from my Sniptide snippets for this fetch call." The agent calls search_snippets, reads the best match with read_snippet and works from your code instead of guessing.

Once an agent connects, the dashboard lists it with the time it last called Sniptide, and a chart shows how often your agents read from your library.

If you would rather keep the patterns in the repository, the CLI installs the same collection as a skill:

sniptide skill snippets

SKILL.md describes each paste, and the agent reads only the files it needs. A skill is a local copy, so run the command again with --force after the collection changes.

How agents reach your pastes

The MCP server runs inside the app at /api/mcp, on sniptide.com and on every self-hosted instance. An agent signs in with OAuth, or with a personal API token for unattended jobs. Read access is the default, and an agent can save or edit snippets only when you grant write access.

An agent only reaches your own pastes, and revoking a token or a connection cuts off access at once. Agents that fetch a link directly can ask for Markdown with Accept: text/markdown and get the files as fenced code blocks, without the page around them.

Where it runs

Use Sniptide on sniptide.com, or run the same app on your own server. Self-hosting takes one command, and the self-hosting guide covers the rest.

curl -fsSL https://sniptide.com/install.sh | sh

Why I built Sniptide

I wasn't happy with the state of pastebins, and our comparison of Pastebin alternatives shows why. Most of them look outdated, and they're missing features I expect from any modern tool. I also wanted one I could self-host without a weekend of setup, so the install is a single command.

And I wanted a pastebin built for the way we write code now, with agents. Your agent should be able to find the snippet you saved last week as easily as you can. That's Sniptide: a pastebin that looks good, feels polished and works for you and your agents.

Where Sniptide is going

The goal is for Sniptide to be the best pastebin and the quickest way to share code. Beyond that, we want it to become a registry for your agents.

Every project rebuilds the same pieces: auth, the database setup, your design patterns. Pull them out once, save them as building blocks in a collection, and your agent can snap them into the next product instead of starting over. Doing that through GitHub today means publishing packages and maintaining versioned registries just to share a few files. In Sniptide it's a paste.

Extensions are planned too, so sharing a link with real content behind it gets even quicker. The vision has the longer version.

Try Sniptide with the snippet you share most often, then connect your agent and ask it to list your collections.