Publish MCP server as npm package and update dashboard middleware#3
Publish MCP server as npm package and update dashboard middleware#3Adhish-Krishna merged 2 commits intomasterfrom
Conversation
Adhish-Krishna
commented
Feb 26, 2026
Adhish-Krishna
commented
- published @simplens/mcp package to npm for the users to use simplens mcp server in their local machine itself with streamable-http or stdio transports.
- update the dashboard middleware to check for authorization header for api related requests if no session is present. Because this request may be made my the mcp server. So that the mcp server can actually access the api routes specific to the dashboard
…th stdio and streamable-http mode using the npm package
…ests for /api requests to allow requests from mcp server
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f75cd89568
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "files": [ | ||
| "dist", | ||
| "README.md" |
There was a problem hiding this comment.
The package now whitelists only dist and README.md, but there is still no prepack/prepare step to run tsc, so publishing from a clean checkout (or CI) produces a tarball without dist/index.js; in that state, both main and bin point to a missing file and npx @simplens/mcp cannot start. This is a release blocker for any publish flow that does not manually build first.
Useful? React with 👍 / 👎.
1 participant
