MCP.so
Sign In

Retasc

@Retasc

About Retasc

The issue tracker AI coding agents pull work from: atomic claims, dependency-aware dispatch, leases, and cross-runtime handoffs. A persistent, dependency-aware, leased work queue a fleet of AI agents pulls from over MCP with server-enforced correctness. Remote server, 33 tools. Self-serve: npm i -g @retasc/cli && retasc login && retasc bind. Docs: https://docs.retasc.com

Connection details

https://mcp.retasc.com/mcp

Setup

claude mcp add retasc --transport http https://mcp.retasc.com/mcp

Tools

No tools detected

Fetch the live tool list directly from this server's endpoint using the button above.

Frequently asked questions

What is the Retasc remote MCP server?

The Retasc remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.retasc.com/mcp, so AI assistants can connect to it without installing or running anything locally.

How do I connect to the Retasc MCP server?

Add the endpoint https://mcp.retasc.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the Retasc MCP server require authentication?

Yes. Retasc requires an API key — check the official documentation for how to obtain one, then include it in your client's configuration.

Which transport does the Retasc MCP server use?

Retasc exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments