list_issues in Continue extension in VS Code with GitHub Docker MCP

list_issues ツールから開始し、提供された GitHub Docker MCP 構成を使って公開リポジトリに対するリクエストを再現します。パラメーター direction が GitHub API に到達するまでを追跡します。完了の条件は、有効な最近の Issue リクエストが OrderDirection エラーで失敗しなくなり、search_issues が引き続き動作する比較対象となることです。

MCP config:

name: GitHub Docker
version: 1.0.1
schema: v1

mcpServers:

• name: GitHub Docker
  command: docker
  flags:
  • secrets
  • github.env
    args:
  • mcp
  • gateway
  • run

Docker preview with 93 tools (a lot of tools there)

Chat with local Qwen3-coder but this goes for GPT-OSS:120b too.

get 3 most recent open issues from paulincai/apps.activitree

I'll help you get the 3 most recent open issues from the paulincai/apps.activitree repository. Let me use the GitHub API to fetch this information.

Continue tried to use the GitHub Docker list_issues tool
I see there's an issue with the GitHub API call. Let me try a different approach to get the recent open issues from the paulincai/apps.activitree repository.

Let me use a more direct method to fetch this information.

what seems to be the issue with GitHub API call?

I'll analyze what went wrong and then work on fetching those issues properly.

The error message indicates there's an issue with the direction parameter in the GitHub API call. It seems like the API is expecting a specific value for the OrderDirection type but received something invalid. This could be due to how the parameters were passed or potentially a temporary API issue.

Let me try a different approach using a simpler query to get those recent open issues.

Continue tried to use the GitHub Docker list_issues tool
I see we're still encountering that same error with the GitHub API. Let me try a different approach to get those issues.

Since we're having trouble with the API call, let me manually check what's available by trying a simpler query method, or I can suggest an alternative way to get this information.

what seems to be the problem?

I see the issue now. The error message "Variable $direction of type OrderDirection! was provided invalid value" indicates that the GitHub API is expecting a specific format for the direction parameter (like "ASC" or "DESC"), but it's receiving an invalid value.

This is likely because the API call is being made with an incorrect parameter format. Let me try a different approach to get the three most recent open issues from the paulincai/apps.activitree repository.

Instead of using the list_issues function, I'll try using a direct search query that doesn't rely on the problematic direction parameter.

---

Let me try a different approach to get the three most recent open issues from the paulincai/apps.activitree repository.

I'll use the search_issues function which should avoid the direction parameter issue we encountered.

Continue used the GitHub Docker search_issues tool
Ah-ha! Success! I've retrieved the 3 most recent open issues from paulincai/apps.activitree. Here they are, sweetly sorted by recency (most recent first):

===================================

Explained by google AI:

The GraphQL error Variable $direction of type OrderDirection! was provided invalid value occurs because the value passed for the $direction variable is not a valid member of the OrderDirection enum. For the GitHub API, the valid values are ASC (ascending) and DESC (descending). This issue is likely happening because the API call from the official MCP Docker is providing a value that the GitHub GraphQL API does not recognize.

Potential causes and solutions

• Incorrect string value: The most common cause is a typo or using a lowercase string. The GraphQL API requires the specific, uppercase enum values ASC or DESC.

• Docker environment variable issue: It's possible that a Docker environment variable used by the MCP is not correctly set or is being passed with an incorrect format, such as extra quotes or other characters.

• Library or tool configuration: The library or tool you're using within the Docker container might be constructing the GraphQL query incorrectly, leading to an invalid value for the $direction parameter.

A better approach for retrieving recent issues

Your proposed solution of switching to a search query that doesn't rely on the $direction parameter is a good one. For the GitHub API, you can achieve this by specifying the sorting directly in the search query.
Here's how you could structure a search query to get the three most recent open issues for paulincai/apps.activitree:
repo:paulincai/apps.activitree is:issue is:open sort:created-desc