Describe the feature or problem you’d like to solve

Add an optional field to allow new issues to specify a Project parameter, so that we can precisely instruct MCP Client to the MCP server to allocate the newly created issue to that project.

Location:https://github.com/github/github-mcp-server/blob/main/pkg/github/issues.go

funcCreateIssue(getClientGetClientFn,t translations.TranslationHelperFunc) (tool mcp.Tool,handler server.ToolHandlerFunc) {

The parameter would be similar to gh command line using GitHub v3 API:https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue

gh issue create --title"My new issue" --body"Here are more details." --assignee @me,monalisa --label"bug,help wanted" --project onboarding --milestone"learning codebase"

Notice the--project parameter

Proposed solution

I was looking into Google Go implementation, but couldn't find "project": inhttps://github.com/google/go-github/blob/master/github/issues.go

The only place seems to be on the repo side:https://github.com/google/go-github/blob/3c5408e78f96138f004621711cac62db14ea030e/github/repos.go#L92

So probably the underlying Google GitHub Go implementation doesn't have this parameter. Would like the author to have a look, I'll investigate further.

Additional context

The use case is very simple and useful, we can summarize a to-do list after a meeting or just vibe-coding, then compare with the to-do list in GitHub Project Kanban board, then automatically update / create new issues. The missing "Project" field will mess up the newly created issues to be ending inside "Issues" of the repo, not "Projects".

For those not aware: in your GitHub Organization page, there's Projects tab. You can create and assign a Project to a Repo, then the Project will appear in your Repo. There are multiple ways of visualize Project, e.g. Kanban Board, Roadmap etc. So we can have separate Projects for business (within the Organization level), while coders can have their Projects within the Repo but still visible to the Organization level.