Skip to main content
Glama
grigoreo-dev

otask-mcp-server

by grigoreo-dev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for HTTP server (default: 3847)3847
OTASK_EMAILNoEmail for O!task API login
MCP_AUTH_TOKENNoOptional Bearer token to protect the MCP HTTP endpoint (for n8n clients)
OTASK_AUTH_KEYNoStatic Bearer token for O!task API authentication
OTASK_PASSWORDNoPassword for O!task API login

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
otask_get_taskA

Fetch a task from O!task by workspace and task slug.

Use before otask_update_task to inspect current field values (board_id, performers, tags, etc.).

Args:

  • ws_slug: Workspace UUID from panel.otask.ru URL (/ws/{ws_slug}/...)

  • task_slug: Task UUID from URL (.../tasks/{task_slug})

Returns JSON with key task fields: id, slug, name, description, end_at, board_id, board_column_id, priority_id, project_id, performers, tags.

Docs: https://api.otask.ru/docs#zadaci-GETapi-v1-ws--ws_slug--tasks--task_slug

otask_update_taskA

Update an existing O!task task. Sends POST /api/v1/ws/{ws_slug}/tasks/{task_slug}/update.

The O!task API requires a full task payload. This tool fetches the current task, merges your changes, then submits the update. Only pass fields you want to change.

Common updates:

  • board_column_id: move task to another column/status

  • name, description, end_at, priority_id

  • performers, tags, subtasks, files

  • comment: optional note recorded with the update

Args:

  • ws_slug, task_slug: UUIDs from panel.otask.ru

  • Any task fields to change (all optional except slugs)

Returns updated task summary on success.

Docs: https://api.otask.ru/docs#zadaci-POSTapi-v1-ws--ws_slug--tasks--task_slug--update

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/grigoreo-dev/otask-mcp'

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