Tool Pipeline Builder

Chain developer tools together — output of one step feeds into the next. Build custom workflows and share them via deep links.

Your data never leaves your browser Available via MCP
0 steps
Input

What Is a Tool Pipeline?

A tool pipeline lets you chain multiple text transformations together in sequence. Instead of copying output from one tool and pasting it into another, you define the steps once and your data flows through them automatically. The output of each step becomes the input of the next.

This is especially powerful for common developer workflows like decoding a JWT token and pretty-printing the payload, or decoding Base64 data that turns out to be JSON that you then want to convert to YAML.

Common Pipeline Examples

  • Decode JWT & Pretty-Print: JWT Decode → JSON Format — paste a JWT token and get a beautifully formatted header and payload.
  • Base64 → JSON → YAML: Base64 Decode → JSON Format → JSON → YAML — decode encoded config data and convert to YAML.
  • JSON → CSV → Base64: JSON → CSV → Base64 Encode — convert API data to CSV and encode for safe transport.
  • Validate & Minify: JSON Validate → JSON Minify → Base64 Encode — verify JSON is valid, strip whitespace, and encode.

Deep-Link Sharing

Every pipeline configuration is encoded into the URL hash fragment. This means you can bookmark your favorite pipelines or share them with teammates by sending a link. The pipeline state — including your input data if you choose — is fully reconstructed when the link is opened. No account or server-side storage needed.

Available Processors

The pipeline supports 30+ processors across multiple categories: JSON formatting, encoding/decoding (Base64, URL, HTML entities), code formatters (HTML, CSS, JavaScript, XML, SQL), converters (JSON↔CSV, JSON↔YAML, Markdown→HTML, JWT decode), and text utilities (uppercase, lowercase, sort lines, remove duplicates, and more).

Not Sure Where to Start?

If you have data but aren't sure what format it is, try Paste Anything first — it auto-detects the format and tells you which tool to use. Once you know the format, come back here to build a multi-step transformation pipeline.

Frequently Asked Questions

What is a tool pipeline?
A tool pipeline chains multiple text transformations together — the output of one step becomes the input of the next. For example, you can decode Base64, then format the resulting JSON, then convert it to YAML, all in one flow.
How do I share a pipeline with someone?
Click the "Share Link" button to copy a URL that encodes your entire pipeline configuration (and optionally your input text) into the URL. Anyone who opens the link will see the same pipeline setup.
Does my data leave my browser?
No. All processing happens 100% client-side in your browser. No data is sent to any server. The pipeline configuration is encoded in the URL hash fragment, which is never sent to servers.
What happens if a step fails?
If any step encounters an error (e.g., invalid JSON for a JSON formatter), the pipeline stops at that step and shows the error message. Fix the issue or remove the failing step to continue.
Can I reorder steps?
Yes! Use the up/down arrow buttons on each step card to reorder steps. You can also remove steps with the × button and add new ones at any position.
What are recipes?
Recipes are pre-built pipeline configurations for common workflows like "Decode JWT & Pretty-Print" or "JSON → CSV → Base64." Click the Recipes button to browse and load them with one click.

Use this tool from AI agents. The CodeTidy MCP Server lets Claude, Cursor, and other AI agents use this tool and 46 others directly. One command: npx @codetidy/mcp

Drop file to load