roo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROO_API_KEY | Yes | Your 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 |
| 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 |
| 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_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 |
| 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 |
| roo_set_webhookA | Fire an HTTP request to |
| roo_set_preview_linkA | Control how the shortlink unfurls on social/chat (Open Graph title/description/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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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