SSyncDev

Mcp-server-celery MCP Server

Read-only Celery debugging: workers, queue depths and stuck-task diagnosis.

Local serverstdio

What is the Mcp-server-celery MCP Server?

Mcp-server-celery is an MCP integration. Read-only Celery debugging: workers, queue depths and stuck-task diagnosis.

Packages and local setup

The published pypi package is mcp-server-celery, version 0.1.0. Its declared MCP transport is stdio.

The package declares CELERY_BROKER_URL (required): Broker URL, e.g. redis://localhost:6379/0 or amqp://user:pass@host:5672//; CELERY_RESULT_BACKEND: Result backend URL, needed for task_status; CELERY_APP: Import path of your Celery app (e.g. proj.celery:app) to pick up its queues and routes; CELERY_INSPECT_TIMEOUT: Seconds to wait for worker replies (default 1.0).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
CELERY_BROKER_URLBroker URL, e.g. redis://localhost:6379/0 or amqp://user:pass@host:5672//Yes
CELERY_RESULT_BACKENDResult backend URL, needed for task_statusCheck documentation
CELERY_APPImport path of your Celery app (e.g. proj.celery:app) to pick up its queues and routesCheck documentation
CELERY_INSPECT_TIMEOUTSeconds to wait for worker replies (default 1.0)Check documentation