Skip to main content
Glama
dzisner
by dzisner

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROO_API_KEYYesYour Roo API key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
roo_whoamiA

Verify the Roo API key and return a compact account summary (email, plan, limits, subscription dates). Use to check that Roo access is working before other operations.

roo_list_shortlinksA

List shortlinks on the account (cursor-paginated, most-recent first). Returns compact items — call roo_get_shortlink for full detail on one.

roo_create_shortlinkA

Create a shortlink that redirects to url. Optionally attach to a custom domain, request a slug, and/or configure add-ons up front. Passing add_ons creates the shortlink AND attaches every listed add-on in a single API call. When add_ons.qr is included, the pre-rendered QR image comes back inline in the response.

roo_get_shortlinkA

Fetch full detail of one shortlink by id — destination, custom domain, click count, permanence, folder, description, and any add-ons.

roo_update_shortlinkA

Update a shortlink. Change the destination URL and/or the custom-domain binding. Only fields you pass are sent. To change add-ons, use the roo_set_* tools; to make/unmake permanent, use roo_make_permanent.

roo_make_permanentA

Mark a shortlink as permanent — it stops participating in the plan's auto-expiry (Hop = 90 days). Counts against the account's permanent-shortlink limit. To un-make a link permanent, use roo_update_permanent_settings with { permanent: false }.

roo_update_permanent_settingsA

Update permanent-mode settings on a shortlink. Today the only verified field is permanent (true/false) — additional fields may be accepted by the endpoint in the future; only fields you pass are sent.

roo_list_custom_domainsA

List every custom domain attached to the account, with each one's status and verification details. Authoritative — this is the same data the Roo web app uses. Distinct from the domain a particular SHORTLINK is on (a shortlink can be on roo.ws or roo.bz — Roo-owned defaults — without any custom domain being attached).

roo_get_qr_codeA

Fetch the QR image for a shortlink. Requires the qrCode add-on to already be configured on the shortlink (via roo_set_qr_addon) — otherwise Roo returns a qr_not_enabled error. By default returns the image inline as an MCP image content block; pass save_to (absolute path) to write the bytes to a file instead.

roo_set_scheduled_redirectA

Time-based redirect: attach or replace waypoints on the shortlink. Each waypoint is a { url, at } pair — at time T the redirect switches to url and stays until the next waypoint. Before the first waypoint the shortlink falls through to its base url. Roo has no timezone or per-waypoint end field.

roo_set_click_count_redirectA

Click-count redirect: attach or replace cumulative thresholds on the shortlink. After the shortlink accumulates click_count clicks, the destination switches to url and stays until the next threshold. Order thresholds by increasing click_count; the tool re-sorts.

roo_set_webhookA

Fire an HTTP request to endpoint on every click. Roo requires 8 fields; this tool defaults 7 of them — you only need to provide the endpoint. The webhook does NOT change where the shortlink redirects to; the destination is unchanged.

roo_set_preview_linkA

Control how the shortlink unfurls on social/chat (Open Graph title/description/image). image accepts either a base64 data URI for a new upload, or a previously-returned image_url to keep the current image.

roo_set_qr_addonA

Configure and enable the QR code add-on on a shortlink. Roo requires all 6 fields; the tool defaults them all. After this succeeds, use roo_get_qr_code to fetch the rendered image.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dzisner/roo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server