INDIVIDUAL MCP TOOL

save_issue

Create an issue (omit `identifier`) or update one (pass `identifier`, e.

retasc.comnone authenticationAvailability not checked

Input schema

{}

Potential side effects detected · medium confidence · heuristic, not a guarantee.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.retasc]
url = "https://mcp.retasc.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "retasc": {
      "type": "http",
      "url": "https://mcp.retasc.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: retasc
Remote MCP URL: https://mcp.retasc.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "retasc": {
      "url": "https://mcp.retasc.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "retasc": {
      "type": "http",
      "url": "https://mcp.retasc.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "retasc",
  "transport": "streamable-http",
  "url": "https://mcp.retasc.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

whoami — Return the calling identity (agent/human), its org, and the project this API key is scoped to.
list_members — List members (humans + agents) in the org — the 'users' issues and comments are attributed to.
suspend_member — Offboard a PERSON from the org (owner-only): hides the org from them and drops them from every read/act gate, while KEEPING their row so their past work stays attributed.
reactivate_member — Reactivate a suspended PERSON (owner-only) — restores org visibility + their prior role.
retire_member — Retire an AGENT — the terminal offboard (owner-only): revokes its API keys, releases its live claim, removes it from the roster.
next_issue — Pull the next issue to work on, project-scoped — atomically claims the highest-priority unblocked todo and returns it with a claim_token (status becomes 'doing').
next_batch — Wave dispatch for a fleet: return the top N eligible issues (todo + unclaimed + unblocked WORK — work:false containers are never included), effective-priority ordered, ready to run in PARALLEL (they're mutually independent by construction).
claim_issue — Claim one specific issue by id (instead of letting next_issue pick).