Where is my order? Let your AI assistant answer it
Connect your shop, carrier and stock database once. The assistant answers order, delivery and stock questions without anyone opening a dashboard.
Tooliganz: give your APIs a job
Turn any API or database into an MCP server
Tooliganz turns a cURL command, OpenAPI spec, Postman collection or SQL query into one URL your AI assistant can call. Works with Claude, Cursor, VS Code and any MCP client. No MCP code, no drama.
Masked, plugged, and ready to work.
- Free plan, no card
- Read-only database access by default
- Self-hosted
1. Paste anything
2. It becomes a tool
POSTpost_orders
3. Your AI uses it
Calling post_orders
0ways to import: OpenAPI, Postman, cURL, SQL
0databases: Postgres, MySQL, SQLite
0lines of MCP code to write
0URL to share with your AI client
Setup walkthrough
From zero to a live MCP server in four steps
Try each step right here. Nothing is saved, and the real dashboard works the same way.
About a minute, start to finish.
Pick a starting point
Paste it. Tools appear.
Try a sample:
Run it before the AI does
GETget_postid = 1
Press “Run test” to call the real endpoint.
Paste one line into your AI client
Client:
Server live. Your AI can now call 6 tools.
Features
Everything between your data and the AI
Hover or tap a tile to flip it and see how it works.
Import anything
OpenAPI, Swagger, Postman, cURL, SQL.
FlipOne operation, one tool
Every endpoint in your spec becomes a tool with typed parameters. Local $refs are resolved, request bodies flattened.
paths: /orders/{id}
→ get_order(id)Tool editor
Rename, rewrite, switch off.
FlipShape what the AI sees
Good descriptions make better tool choices. Edit names, descriptions and parameters, or hide risky tools entirely.
delete_order [off] get_order [on]
API auth built in
Keys stay on your server.
FlipBearer, header, query, basic
Credentials are added server-side on every call. They are never returned by the API or shown to AI clients.
Authorization: Bearer ••••
Secured endpoints
A token per server.
FlipRotate any time
Every server gets its own access token. Rotate it in one click, or turn the server off completely.
claude mcp add … --header "Authorization: Bearer …"
Database queries
Postgres, MySQL, SQLite.
FlipRead-only by default
Write a query with :named parameters. Values are bound, never spliced into the SQL, and sessions run read-only.
SELECT * FROM orders WHERE customer = :customer
Test runner
Try every tool first.
FlipSee the real response
Run any tool from the dashboard with sample arguments and read the status, latency and body before an AI ever calls it.
200 OK · 184 ms
Analytics
Calls, errors, latency.
FlipKnow what the AI does
A live call log and 30-day stats per server: volume, error rate and median latency, plus your monthly quota.
1,204 calls · 0.4% errors
Private by design
Arguments never stored.
FlipMetadata only
Logs hold the tool name, status, duration and error text. Arguments and responses are never written to disk.
tool · 200 · 184 ms
What it looks like
Ask in plain English. Your systems answer.
Pick an example to watch an AI assistant use tools built with Tooliganz.
Manage with AI
Ask Claude to build your servers
Tooliganz is an MCP server too. Give an AI agent an API key and it can create servers, import tools, set credentials and report on usage, all from a conversation.
- Keys are created by administrators and can be read-only
- Revoke any key in one click, or switch the feature off for the whole app
- Agents only reach their own account, and plan limits still apply
Create an MCP server from this cURL command and give me the URL.
tooliganz · create_server
{ "name": "Orders",
"tools_added": 1,
"endpoint": "https://you.example/mcp/orders-3f9a1c" }Done. Your Orders server is live with one tool. Want me to add a token and set the API key?
Use cases
Built for how teams actually work
From shops to clinics to agencies, see how people give an assistant safe access to the systems they run.
A finance copilot that can read everything and change nothing
Payments, ledger and accounting in one place for month-end questions, with read-only connections and writes held for a person to approve.
A scheduling assistant that never touches patient records
Open slots, bookings and opening hours are an API call away. Clinical records stay out of reach by design.
Dispatch questions in plain English
Ask where a load is, which dock is free and which driver is nearest, drawn live from the transport system, GPS feed and warehouse database.
Claims that triage themselves, with a person on the payout button
Answer cover questions from the policy system and draft claim notes, while anything that moves money waits for a human.
One gateway, many client APIs
A different set of APIs for every client becomes one endpoint per client, with separate tokens and separate usage.
Pricing
Start free. Upgrade when you outgrow it.
Solo
Free
- 1 server
- 10 tools
- 1,000 calls a month
- All four importers
- Database queries
Pro
$49 / year
- Unlimited servers
- Unlimited tools
- Unlimited calls
- Everything in Solo
- Priority email support
FAQ
Questions, answered
Do I need to write code?
No. Paste a spec, a cURL command or a SQL query and you get working tools. You can edit anything in the dashboard.
Which AI clients work?
Any client that supports remote MCP over Streamable HTTP, including Claude, Cursor and VS Code.
Can the AI change my database?
Not unless you allow it. Database servers are read-only by default: only a single SELECT-style statement is accepted, and the session itself is read-only where the database supports it.
Where does it run?
It is a self-hosted Node app with a SQLite file. Run it on a laptop, a server or a container.
Are my API keys safe?
Upstream credentials stay on your server. They are never returned by the API or sent to MCP clients.
What do you store?
Configuration and call metadata only. Tool arguments and API responses are not logged.
Masked, plugged, and ready to work.
Time to put your APIs to work
Create your first Tooliganz server in about a minute.