specup.setup

/specup.setup

First-time setup for specup. Verifies the ClickUp MCP server is reachable and authenticated, then saves the default ClickUp Space (and optional parent Folder) for this project so that /specup.export and /specup.new know where to operate without asking each time.

Workflow

1) Verify ClickUp MCP server connectivity

Run a lightweight read-only MCP call to confirm the server is reachable and the user is authenticated. A good candidate is listing workspaces/teams, or fetching the authenticated user:

1. Try calling clickup_get_teams (or clickup_get_authorized_teams, clickup_get_user, or whichever read-only tool is available).
2. Parse the response.

If successful:

ClickUp MCP: connected
User: {name or email from response}
Teams: {team names}

If the call fails or the tool is not found:

• If the error indicates auth failure (401, token invalid, OAuth expired): instruct the user to re-authenticate:

  ClickUp MCP server returned an authentication error. Re-run OAuth by restarting your editor or re-adding the MCP server. Config location: .mcp.json (should contain https://mcp.clickup.com/mcp)

• If the MCP server itself is unreachable (connection refused, tool not registered): confirm .mcp.json exists and contains the clickup entry, then stop:

  ClickUp MCP server is not available. Ensure .mcp.json includes:

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

  Then restart your editor to load the MCP server.

Stop here if connectivity or auth fails. The remaining steps require a working connection.

2) List available Spaces

Once authenticated, fetch the user's Spaces:

1. Call clickup_get_spaces (or equivalent) for the team/workspace from step 1.
2. Present a numbered list:

Available Spaces:

1. Engineering (id: 12345)
2. Product (id: 67890)
3. Personal (id: 11111)

Which Space should specup use as the default for this project?
(Enter number, Space name, or Space ID)