TinyURL integration for AI agents.
TinyURL integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves TinyURL tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real TinyURL actions, managed and audited.
Your user connects TinyURL once; your agent can then uRL Shortener, Branded Short Links & Analytics — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants TinyURL access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported TinyURL tools.
21 tools are generated from the published TinyURL catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 21 tools. All published catalog entries are included in this page's server-rendered HTML.
- Enable/disable TinyURL analytics sharing
- Endpoint allows to manage TinyURL analytics sharing
- TinyURL
- Enable/disable TinyURL analytics collecting
- Endpoint allows to manage TinyURL analytics collecting
- TinyURL
- Archive/unarchive TinyURL
- Endpoint allows to archive/unarchive TinyURL
- TinyURL
- Return a bulk request report
- Return a bulk request report
- Bulk
- Return a bulk request status
- Return a bulk request status
- Bulk
- Create a new TinyURL processing batch
- Crteates new batch
- Bulk
- Update TinyURLs long URL
- Endpoint allows to update TinyURL long URL
- TinyURL
- Create a new TinyURL
- Take a long URL and shorten it into a new TinyURL.
- TinyURL
- Delete TinyURL
- Endpoint allows to delete TinyURL
- TinyURL
- Return browser, os and device analytics
- Return browser, os and device analytics
- Analytics
- Receive TinyURL information
- Endpoint allows to receive TinyURL information
- TinyURL
- Get count of TinyURLs
- Endpoint allows to get a count of TinyURLs
- TinyURL
- Get a list of TinyURLs
- Endpoint allows to get a list of TinyURLs
- TinyURL
- Return hour popularity analytics
- Return hour popularity analytics
- Analytics
- Return location analytics
- Return locations analytics
- Analytics
- Return raw analytics logs
- Return raw analytics logs
- Analytics
- Return timeline analytics
- Return timeline analytics
- Analytics
- Return top languages analytics
- Return top languages analytics
- Analytics
- Return top sources analytics
- Return top sources analytics
- Analytics
- Update TinyURLs alias, tags, stats options
- Endpoint allows to update TinyURL alias, tags, stats settings
- TinyURL
- Return week days popularity analytics
- Return week days popularity analytics
- Analytics
TinyURL integration, answered
- How do AI agents use TinyURL through Open Connector?
- Your user connects TinyURL once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes TinyURL tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a TinyURL MCP server?
- Yes. Open Connector can serve TinyURL as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call TinyURL actions with credentials injected server-side.
- Where do TinyURL credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents TinyURL — keep the keys.
Open source, self-hostable, with TinyURL credentials that never leave your infrastructure. Run it from source today.