Plan issue retrieval
Prepare an HTTP or code step against GitHub’s repository-issues API, with repository access, pagination and filtering for issues versus pull requests.
Your connection path
GitHubVS Code
Stacksync MCP OAuth
Your assistant builds a workflow for the app’s API. API access and configuration are required.
First request
“Plan a repository issue digest”
Stacksync MCP · Custom API workflow
Connect GitHub to VS Code with MCP.
Build a GitHub workflow through Stacksync MCP using documented HTTP or code steps when the required action is not in the live catalog. The reviewed public catalog does not establish a native GitHub connector, so these examples are custom integration plans.
01 / The connection
How GitHub works with VS Code
Build a GitHub workflow through Stacksync MCP using documented HTTP or code steps when the required action is not in the live catalog. The reviewed public catalog does not establish a native GitHub connector, so these examples are custom integration plans. Add the Stacksync MCP server to VS Code, then use the custom workflow path below.
This guide connects GitHub through a custom Stacksync workflow. It does not provide a prebuilt GitHub MCP server.
Explore the GitHub connector →02 / Capabilities
GitHub capabilities through MCP
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Draft issue creation
Design an issue-creation request with the target repository, title, body and duplicate detection before any write is executed.
Prepare issue comments
Propose a comment workflow using an existing issue number and exact content, with a check that the comment has not already been posted.
03 / Setup
Set up Stacksync MCP in VS Code
Connect the MCP server first. Then configure a custom workflow for the GitHub API using the requirements below.
Code editorVS Code
Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- VS Code with Copilot Chat Agent mode available.
Add Stacksync to VS Code
Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.
code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}'Start it in Copilot Chat
Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for GitHub; configure API access and secure credentials outside chat before testing that workflow.
04 / Put it to work
GitHub workflow prompts
Example prompts for GitHub in VS Code. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
01
Custom API workflow
Plan a repository issue digest
Check the Stacksync catalog for a GitHub action first. If the needed action is absent, inspect available HTTP or code steps and propose a workflow using GitHub’s repository-issues API for the repository I choose. Include authentication outside chat, pagination and exclusion of pull requests. Show the request and digest fields before saving or running anything.
What to expect
A custom issue-digest design with an explicit repository and complete-result handling.
02
Custom API workflow
Design a support-to-issue handoff
Inspect my existing support workflows and check for the required GitHub modules. If a custom path is needed, propose an HTTP or code step to create a GitHub issue from a support escalation. Include the source ticket ID for duplicate prevention, the repository, issue title and a redacted body. Wait for review before creating a workflow or issue.
What to expect
A custom escalation proposal with a stable source reference and a reviewable issue payload.
03
Custom API workflow
Prepare an issue status comment
Check the available GitHub actions and the issue number I provide. If no native action fits, propose a custom HTTP step using the GitHub issue-comment API. Show the repository, issue URL, exact comment and a check against posting the same update twice. Do not save, deploy or submit the comment until I approve.
What to expect
A precise comment proposal with target and duplicate checks, ready for implementation review.
05 / Before you run
Requirements and limitations
What you need
- Connect your AI client to Stacksync MCP, sign in and select the workspace before inspecting its resources.
- Identify the GitHub owner and repository, plus the permission needed for the intended issue operation.
- For a custom API step, configure authentication outside chat using approved secrets or a supported connection. Verify the live catalog before choosing a custom implementation.
What to account for
- GitHub is absent from the reviewed public app catalog. This is not evidence of a ready-made native Stacksync GitHub MCP tool.
- Custom HTTP or code workflows require endpoint configuration, authentication and testing. Deploying a reusable custom connector is a separate development and review process.
- GitHub’s issues API can also return pull requests; reports must filter them deliberately and follow pagination.
Your workspace. Your permissions.
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗If setup does not work
- The MCP server does not appear
- Check your client’s custom MCP settings and any plan or administrator prerequisites. Reconnect using the setup instructions above.
- Your workspace or app is missing
- Verify the Stacksync account and workspace selected during OAuth, then check the live catalog. For this custom workflow, configure HTTP or code steps and provide the required API credentials through approved secret storage outside chat.
- An action is unavailable or denied
- Check the workflow configuration, API version, required inputs and app token permissions. Confirm that your Stacksync role and OAuth consent allow the proposed workflow changes.
06 / Common questions
GitHub MCP questions
Does Stacksync have a verified native GitHub MCP connector?
The reviewed public app catalog does not list GitHub. Check the live catalog because it can change. The path documented here uses Stacksync’s custom HTTP or code workflow capability.
How is this different from GitHub’s own MCP server?
This page describes an assistant configuring or running work through Stacksync. A custom GitHub API step must be built and authenticated; it does not install GitHub’s separate MCP server.
Can I create issues without exposing credentials in a prompt?
Yes, the custom workflow design keeps credentials in approved secrets or connection settings. Do not paste a GitHub token into the chat or embed it in a workflow’s source text.
Reviewed · Product documentation and connector references
Keep building
