[Bug]: Locally created MCP Server do not work with Copilot adapter

[Lumean97]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

Not sure

Steps to reproduce

Summary

A locally developed stdio MCP server is recognized and callable from Copilot CLI, but the same server is not recognized by t3code when configured through the MCP feature.

Reproduction repo

https://github.com/Lumean97/t3code-local-mcp-reproduction

Reproduction steps

1. Clone the repo.
2. Run npm install.
3. Run npm run build.
4. Add the built server to Copilot MCP config with node + the absolute path to dist\index.js.
5. In Copilot CLI, ask to use the forge_badge MCP tool.
6. In a t3code session with the same MCP configuration, ask to use the same tool.

Notes

• The reproduction server is intentionally minimal and only exposes one trivial tool (forge_badge) to keep the issue focused on MCP registration/discovery.
• The repo also includes a smoke test (npm run smoke) that proves the local MCP server itself is valid and callable outside of t3code.

Expected behavior

t3code should discover and call the same local MCP server exactly like Copilot CLI does.

Actual behavior

• Copilot CLI recognizes the MCP server and successfully calls forge_badge.
• t3code does not recognize the MCP server / tool appears unregistered or unavailable.

Impact

Minor bug or occasional failure

Version or commit

No response

Environment

No response

Logs, stack traces, or screenshots

Workaround

No response

[zortos293]

#28

[zortos293]

can you try with latest version?

[zortos293]

[Lumean97]

Worked for me. Thanks for the update, really hard appreciate it!

[zortos293]

there are some icon issues atm will be fixed in next update