Runrun.it MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNRUNIT_APP_KEY | Yes | Your Runrun.it API App Key | |
| RUNRUNIT_USER_TOKEN | Yes | Your Runrun.it User Token |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_taskB | Get core information about a specific task (Title and Description). Use this for general context about what needs to be done. |
| get_task_detailsA | Get the FULL, raw API response for a task. WARNING: This is very large. Only use if you specifically need technical fields, custom field values, or deep task metadata not available in get_task. |
| list_tasksA | List tasks with optional filters. Returns simplified task objects. Use this to find tasks by user, project, or status. |
| get_config_statusB | Check if environment variables are correctly loaded (MASKED) |
| get_meA | Get information about the current authenticated user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
get_task and get_task_details overlap in retrieving a task, but the descriptions clearly distinguish core fields from the full raw API response with a size warning. The remaining tools (get_me, list_tasks, get_config_status) have distinct, non-overlapping purposes.
All tool names use snake_case with consistent get_/list_ verb prefixes: get_task, get_task_details, get_me, list_tasks, get_config_status. The pattern is predictable throughout, including the slightly longer config-status tool.
Five tools sits at the low end but still within a reasonable range for a focused integration. It covers task retrieval, user identity, and server configuration, though it leaves little room for broader Runrun.it workflows.
The surface only supports read access to tasks; there are no create, update, or delete task operations. No tools cover comments, projects, time tracking, or other core Runrun.it entities, creating significant dead ends for real task management workflows.