Skip to main content
Glama
Arclio

github-projects-mcp

by Arclio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENYesGitHub personal access token with access to Projects (V2) and the GraphQL API.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsC

List GitHub Projects V2 for a given organization or user.

Args:
    owner: The GitHub organization or user name

Returns:
    A formatted string with project details
get_project_fieldsB

Get fields available in a GitHub Project V2, including options for SingleSelect fields.

Args:
    owner: The GitHub organization or user name
    project_number: The project number

Returns:
    A formatted string with field details.
get_project_itemsA

Get items in a GitHub Project V2. Can filter by state OR a single custom field=value.

Args:
    owner: The GitHub organization or user name
    project_number: The project number
    limit: Maximum number of items to return (default: 50). When filtering, the system automatically fetches more items to improve efficiency.
    state: Optional state filter (e.g., "OPEN", "CLOSED"). Applies to Issues/PRs.
    filter_field_name: Optional custom field name to filter by (e.g., "Status"). Currently supports SingleSelect and Iteration fields.
    filter_field_value: Optional custom field value to filter by (e.g., "In Development"). Uses case-insensitive matching.
    cursor: Optional cursor for pagination. Use value from previous results to get next page.

Returns:
    A formatted string with item details.
create_issueA

Create a new GitHub issue.

Args:
    owner: The GitHub organization or user name
    repo: The repository name
    title: The issue title
    body: The issue body (optional)

Returns:
    A formatted string with the created issue details
add_issue_to_projectC

Add an existing GitHub issue to a Project V2.

Args:
    owner: The GitHub organization or user name that owns the project
    project_number: The project number
    issue_owner: The owner of the repository containing the issue
    issue_repo: The repository name containing the issue
    issue_number: The issue number

Returns:
    A formatted string confirming the addition
update_project_item_fieldB

Update a field value for a project item.

Args:
    owner: The GitHub organization or user name
    project_number: The project number
    item_id: The ID of the item to update
    field_id: The ID of the field to update
    field_value: The new value for the field (text, date, or option ID for single select)

Returns:
    A confirmation message
create_draft_issueC

Create a draft issue directly in a GitHub Project V2.

Args:
    owner: The GitHub organization or user name
    project_number: The project number
    title: The draft issue title
    body: The draft issue body (optional)

Returns:
    A confirmation message with the new draft issue details
delete_project_itemB

Delete an item from a GitHub Project V2.

Args:
    owner: The GitHub organization or user name
    project_number: The project number
    item_id: The ID of the item to delete

Returns:
    A confirmation message

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have distinct purposes targeting different aspects of GitHub Projects V2 management, with clear separation between project-level operations (list_projects, get_project_fields) and item-level operations (add_issue_to_project, update_project_item_field). However, create_issue and create_draft_issue could potentially cause confusion as both create issues, though in different contexts (repository vs. project).

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., add_issue_to_project, create_draft_issue, get_project_items). The naming is predictable and follows logical conventions, making it easy to understand each tool's function from its name alone.

Tool Count5/5

With 8 tools, this server is well-scoped for GitHub Projects V2 management. The count provides comprehensive coverage without being overwhelming, including essential operations for listing, creating, updating, and deleting project items, as well as project-level metadata retrieval.

Completeness4/5

The tool set covers most core GitHub Projects V2 workflows effectively, including project listing, item management, field operations, and issue integration. A minor gap exists in the lack of a tool to remove issues from projects (only delete_project_item for general items), but agents can work around this using existing tools for most scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources