Support + FinanceRefund console
Find the customer, verify the order, calculate the refundable amount, and submit an approval-backed refund.
Customer Postgres · Billing API
read + explicit write
where agent-built tools land
Little tools,
treated like real software.
Your team already builds internal tools from the desktop. Drop each one into the workspace — one sign-in, approved company data, hosting, permissions, versions, and an audit trail — instead of leaving it in a folder, a preview URL, or somebody’s laptop.
free for 3 workspace members · Team includes 15 · Pro includes 50
$ tooldrop init refund-console
✔ scaffolded — login, storage + env rules included
$ claude
✳ building… “make a refunds console for support”
$ tooldrop deploy
✔ refund-console v4 is live
→ tools.yourteam.com/refund-console
→ shared login, approved data, audit trail ▌
workspace auth built in
live in one deployrefund consolechurn radardeal deskon-call rotationcommission trackercustomer 360QA triage boardinventory pulsepricing calculatorSLA monitorlead routerusage explorerrefund consolechurn radardeal deskon-call rotationcommission trackercustomer 360QA triage boardinventory pulsepricing calculatorSLA monitorlead routerusage explorer
From “I made a thing”
to “the team can use it.”
01
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.
02
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.
03
tooldrop deployDrop it in
The tool lands in the workspace: one URL, one login, version history, rollback, and access your team can understand.
Want the whole machine — the scaffold, the request path, versions, roles, day-two ops? Take the full tour →
real internal workflows
Small apps. Real systems of record.
Each app gets only the approved data it needs. The agent can build the workflow without receiving a production credential.
Support + Finance
OperationsInventory approvals
Surface stock exceptions, show the evidence behind each one, and let an authorized operator approve the correction.
Warehouse MySQL · Support API
scoped write
Customer successWeekly account report
Join customer health and warehouse activity into a focused review queue with notes stored in the app.
Customer Postgres · Warehouse MySQL
read only
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.
Approved data, not copied secrets
Connect a database or API once, keep credentials encrypted, and grant each app read or write access. Agents see safe schema metadata—not passwords or tokens.
Tool Storage for app state
Saved filters, notes, and small app-created records live in Tool 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 attach approved data resources without receiving the credentials.
- Required resources and access levels are declared in tooldrop.json before deploy.
- 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 place to land.
The next dashboard, console, or tiny workflow does not need to become another loose app. Build it with your agent, then drop it where the team can trust it.