Skip to content

Add support for Projects #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
toby opened this issue Mar 27, 2025 · 6 comments
Open

Add support for Projects #44

toby opened this issue Mar 27, 2025 · 6 comments

Comments

@toby
Copy link
Member

toby commented Mar 27, 2025

From @LadyNaggaga:

Add support for get_project_board or analyze_project_board tool where devs , leads, PMs can look at the status of work item in copilot.

@vongohren
Copy link

Just to connect the two tasks: #117

@SamMorrowDrums SamMorrowDrums marked this as a duplicate of #117 Apr 15, 2025
@moonray
Copy link

moonray commented Apr 21, 2025

I have a basic implementation working locally based on the original modelcontextprotocol repo. I'll try to work on getting it ported to this new repo.

@deweyjose
Copy link

I'd like the ability to add issues to a project. Right now when I create issues via the MCP server project is not specified. Is this a completely different request? Happy to create a different issue.

@hillaryke
Copy link

hillaryke commented May 2, 2025

At Arclio, we're excited to share Github Projects MCP Server to manage projects. We also needed this functionality for our own projects, so we created this MCP Server which is open-source:
https://github.com/Arclio/github-projects-mcp

This MCP server lets you:

  • List and manage Projects V2 for users/orgs
  • Work with project items (issues, PRs, drafts)
  • Create issues and add them to projects
  • Update project item fields i.e moving a ticket across the board.

Feel free to check it out and give a star if you find it helpful or interesting.

@sirkitree
Copy link

possibly related since i understand Projects to be on GraphQL: #338

@bczegeny
Copy link

Will this support status for items in a project, start and end dates?

Statuses very from project to project, and are not shared across projects at an org level.
Dates tend to also have a variety of labeling names
Labels: Start, End, Start date, End Date, Target Date, Delivery Date

Will the tool calls be flexible enough to service prompts like:

  • Tell me whats over due this week?
  • Write me a weekly update on progress this week?
  • Tell me what team member has too much work on their plate? (this should look for # of assigned issues, any custom fields around priority, story points, number of sub issues and progress etc?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants