The actual internal ID for issue #8 is <redacted>, not 8.

  So when I called add_project_item with item_id: 8, it added global issue ID 8 from GitHub's database - which happens to be that random maddox/app_wiki issue from years ago.

  This is a bug/ambiguity in the MCP tool's API design - the parameter should either:
  - Accept issue number + repo context, OR
  - Be clearly documented as requiring the global ID

  I apologize for the confusion. You should remove that random issue from your project manually. When we add issues going forward, I'll use the full internal ID (<redacted>) instead of the issue number.

> is this is a claude code issue or a github mcp issue?

⏺ This is a GitHub MCP server issue (the tool provided by GitHub), not a Claude Code issue.

  The problem is in how the add_project_item tool is designed:
  - The parameter is called item_id with description "The numeric ID of the issue or pull request to add"
  - But it doesn't clarify whether this is the issue number (e.g., #8) or the global database ID (e.g. <redacted>)
  - There's no parameter to specify which repository the issue belongs to

  This ambiguity in GitHub's MCP tool design caused it to interpret 8 as a global GitHub issue ID rather than issue #8 in your repo.

  You could report this to GitHub at their MCP server repo: https://github.com/github/github-mcp-server/issues

  The fix would be either:
  1. Accept owner, repo, and issue_number parameters (clearer), OR
  2. Better document that item_id requires the global numeric ID, not the issue number