Read-only Celery debugging: workers, queue depths and stuck-task diagnosis.
To add mcp-server-celery to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 4 environment variables, listed below.
Install
uvx mcp-server-celery@0.1.0Environment variables
CELERY_BROKER_URLSet in your MCP configCELERY_RESULT_BACKENDSet in your MCP configCELERY_APPSet in your MCP configCELERY_INSPECT_TIMEOUTSet in your MCP configInstall with your client
claude mcp add mcp-server-celery --env CELERY_BROKER_URL=<YOUR_CELERY_BROKER_URL> --env CELERY_RESULT_BACKEND=<YOUR_CELERY_RESULT_BACKEND> --env CELERY_APP=<YOUR_CELERY_APP> --env CELERY_INSPECT_TIMEOUT=<YOUR_CELERY_INSPECT_TIMEOUT> -- uvx mcp-server-celery@0.1.0
Run this in a terminal to add the server to Claude Code.
What this does
mcp-server-celery exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server needs the following environment variables to be set before it can run:
CELERY_BROKER_URL CELERY_RESULT_BACKEND CELERY_APP CELERY_INSPECT_TIMEOUT
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install mcp-server-celery?
Run the Claude Code command in the install section to add mcp-server-celery to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with mcp-server-celery?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to mcp-server-celery as well.
Does mcp-server-celery need an API key?
Yes. Before it can run, set these environment variables: CELERY_BROKER_URL, CELERY_RESULT_BACKEND, CELERY_APP, CELERY_INSPECT_TIMEOUT. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-taltal-beep-mcp-server-celery)<a href="https://clauderules.net/mcp/io-github-taltal-beep-mcp-server-celery" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-taltal-beep-mcp-server-celery" alt="Listed on clauderules.net" /></a>More DevTools MCP servers
Awesome MCP Servers by punkpeye
A curated, community-maintained list of Model Context Protocol (MCP) servers, organized by category, with sections for MCP clients, tutorials, and community resources. The repository is a directory of production-ready and experimental servers that extend AI capabilities through file access, database connections, and API integrations; it is a list, not a runnable MCP server itself.
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
FastMCP
🐍 - A high-level framework for building MCP servers in Python
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.