CommandCodeAI / CommandCodeAI/command-code

Not able to run stitch-with-google through MCP

Open
#393 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

p2
Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

Description

Summary
  1. i ran cmd mcp add --transport http private-api https://api.company.com/mcp
    --header "X-API-Key: your-key-here" in my commandprompt terminal
    after i can find the mcp when i ran /mcp
    but when i mentiod it in my prompt to commandcode, then this is what i got ---- "I don't have a "stitch" MCP server available in my tool set — it's configured in your MCP settings but not surfaced as a tool I can
    call directly."
Image
Expected Behavior

should be able to connect & run stitch successfully.

Actual Behavior

respones from the terminal - "I don't have a "stitch" MCP server available in my tool set — it's configured in your MCP settings but not surfaced as a tool I can
call directly."

Image
Steps to reproduce the issue
  1. cmd mcp add --transport http private-api https://api.company.com/mcp
    --header "X-API-Key: your-key-here" , run in the normal terminal(command prompt or powershell)
  2. then run commandcode, then /mcp, then chose stitch , then activate
  3. open any project, and run commandcode inthis project and prompt it to design some page and use mcp stitch
  4. expected behavior will be there.
Command Code Version

Microsoft Windows [Version 10.0.26200.8457]
(c) Microsoft Corporation. All rights reserved.

C:\Users\V2Khan\temp>

Operating System

Windows

Terminal/IDE

vscode

Shell

cmd.exe

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported mcp add and /mcp flow in Windows Command Prompt or PowerShell with VS Code, then inspect the MCP command entry points. Done means the configured Stitch server is surfaced as an available tool and can be invoked from a project prompt; the issue names no files or tests to start from.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
cli, developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.