Where it fits
Development teams coordinating multiple AI coding agents on shared issues that need to prevent duplicate work.
- Install the Retasc skill for a client.
- Bind a project folder with the CLI.
- Prevent two agents from holding one issue.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Retasc
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Dispatches one agent per independent problem domain so unrelated failures can be investigated concurrently, then reviews and integrates the results. Use it when failures are separate, need no shared context, and can run without interfering.
For carrying out an implementation plan inside the current session, with the agent acting as the implementer itself. That happens when the human partner picked inline execution or when no subagent tool is available.
Helps decide how to integrate finished work after implementation and passing tests. Presents structured choices for merging locally, pushing and creating a pull request, or keeping the branch.
No skills found
Try a different search term or clear the filters.
Retasc CLI bind
The provider documents a skill install plus bind inside the project folder. It does not document the raw mcp.retasc.com/mcp endpoint, so the CLI path is primary and the endpoint is unconfirmed.
- Install the skill
Follow the provider repository to install the Retasc skill for your client.
- Bind the project folder
Run the bind command in the folder that contains the project.
npx @retasc/cli@latest bind
This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
- The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Retasc repositoryhttps://github.com/Retasc/skills