[noskills] Codex MCP client for `noskills` failed to start

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
node.js, typescript
Domain
devtools

Research direction

No source files or tests are named. Start with the MCP configuration generated by npx eser@latest noskills init for Codex, then trace the server startup and initialize handshake used by Codex CLI. Done means the configured noskills MCP client starts without the reported warning.

Written by the indexing model from the issue text.

Description

bug triage
Bug Description

I installed noskills using the npx eser@latest noskills init command in my project, chose Codex (and some others) from the provider options.

Then, in a new Terminal tab, I opened Codex CLI and got this following warning:

MCP client for `noskills` failed to start: MCP startup failed: handshaking with MCP server failed: connection closed: initialize response
Steps to Reproduce
  1. Install noskills with npx eser@latest noskills init
  2. Choose Codex (and optionally some other providers) from the provider options
  3. Finish the installation.
  4. Open a new Terminal tab, and run Codex CLI.
  5. Notice the warning:
MCP client for `noskills` failed to start: MCP startup failed: handshaking with MCP server failed: connection closed: initialize response
Expected Behavior

I expect MCP to work without receiving any warnings

Actual Behavior

MCP startup failed

Runtime

Node.js

Package Version

4.1.56

Runtime Version

Node v24.14.1

Additional Context

No response

Dominant language
TypeScript
Stars
128
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from eser/stack

All issues in eser/stack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.