Little tools,
treated like real software.
Your team already builds internal tools with Claude Code or Codex. Tooldrop gives each one a home in the workspace — one sign-in, Block Storage, platform env vars, hosting, versions, and sharing — instead of a folder, a preview URL, or somebody’s laptop.
free for 2 workspace members · app-only guests get 2 tools
workspace auth built in
live in one deployFrom “I made a thing”
to “the team can use it.”
tooldrop initStart in the right place
One command gives the tool a sanctioned scaffold: the SDK, sign-in contract, storage and env rules, and AGENTS.md your coding agent can actually follow.
claudeBuild with your agent
Use Claude Code, Codex, or whatever your team already likes. Tooldrop isn't the IDE — it's everything around the app once it exists.
tooldrop deployGive it a real home
The bundle ships from your laptop into the workspace: one URL, one login, version history, rollback, and access your team can understand.
Everything around the app, handled.
Your agent builds the interface. Tooldrop owns the parts that decide whether the team can actually trust the tool.
One login for every tool
Teammates use the workspace sign-in they already have. Every tool sits behind the gateway, private to the workspace by default, with signed identity on every request.
Env vars, not copied secrets
Database URLs, API keys, OAuth credentials, and MCP endpoints live as encrypted app env vars. Builders tag them so agents can find the right keys.
Block Storage for app state
Saved filters, notes, and small app-created records live in Block Storage instead of getting written into a production database.
A real address
Every tool gets a stable place in the workspace instead of another preview link drifting through Slack.
Versions, rollback, ownership
Every deploy is kept with who shipped it and what changed. Roll back, clone, or hand off the tool without guessing which folder is current.
Rules your agent can use
The scaffold and MCP server tell Claude or Codex how to query data, where identity comes from, and what not to touch.
What the workspace
stops accumulating.
- Passing around raw preview links as if they were production
- Copying database URLs into another local .env file
- Rebuilding login for one CRUD page
- Wondering who owns refund-console-final-final
- Buying seats for people who only need to click the tool
- Letting every agent guess the data rules
What it involves: tooldrop deploy
A sanctioned path for useful side tools.
- Builders use tagged env vars instead of special connection setup.
- Required keys are declared in tooldrop.json before teammates rely on it.
- Every app opens behind workspace auth, not a forgotten public URL.
- Every deploy has source, owner, version, rollback, and audit history.
Give the next tool a home.
The next dashboard, console, or tiny workflow does not need to become another loose app. Build it with your agent, then put it where the team can trust it.