Build MCP servers using Node.js with automatic tool discovery, Zod schemas, and support for HTTP or stdio transports.
Also known as eliware/mcp-server, @eliware/mcp-server
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- 824
- Latest version
- —
- Last commit
- Oct 27, 2026
- License
- MIT
What is @eliware/mcp MCP?
@eliware/mcp builds MCP servers using Node.js with automatic tool discovery, Zod schemas, and support for HTTP or stdio transports.
Summary generated from the project's README
About @eliware/mcp MCP server
This Node.js package allows developers to build Model Context Protocol servers using a pure-ESM approach. It is designed for those working with Node.js 26 or later who need to implement tool discovery and structured input validation. The framework supports both stdio and Streamable HTTP transports, though it does not support HTTP with SSE.
Developers can define tool input schemas using Zod by importing the z object directly from the package. The system automates tool discovery by scanning .mjs modules placed within a tools directory. For security, the server provides several authentication options including static bearer tokens, bearer passthrough, and generic OAuth2 support. It also allows for injectable context and TLS for remote connections.
To use this, you install the package via npm and configure your server using the mcpServer function. You must ensure your MCP client supports protocol revision 2026-07-28 and the specific transport method you have chosen.
What you can do with it
- 1Automate tool registrationA developer can automatically load multiple tool modules by placing .mjs files into a specific directory.
- 2Validate tool inputsYou can use Zod schemas to ensure that the data sent to your tools follows a strict structure.
- 3Secure remote connectionsYou can protect your server from unauthorized access using bearer tokens or OAuth2 introspection.
- 4Implement flexible communicationYou can choose between local stdio communication or remote Streamable HTTP transports.
Written from the project's README. Every use case is checked against a quote from it.
How to install @eliware/mcp MCP
Formats verified 10 Nov 2026Add to CursorInstall @eliware/mcp MCP in Claude Code
$ claude mcp add mcp-server -- npx -y @eliware/mcp-serverInstall @eliware/mcp MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@eliware/mcp-server"
]
}
}
}Install @eliware/mcp MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@eliware/mcp-server"
]
}
}
}Install @eliware/mcp MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@eliware/mcp-server"]}'Install @eliware/mcp MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@eliware/mcp-server"
]
}
}
}Install @eliware/mcp MCP in Codex
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@eliware/mcp-server"]
Install @eliware/mcp MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@eliware/mcp-server"
]
}
}
}Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableeliware/mcp-server is public and reachablegithub.com/eliware/mcp-server ↗Pass
- Package names this repository as its source@eliware/mcp-server names eliware/mcp-server as sourcenpmjs.com/package/@eliware/mcp-server ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @eliware/mcp-servernpmjs.com/package/@eliware/mcp-server/v/15.0.1#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-27github.com/eliware/mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @eliware/mcp-serverPass
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@eliware/mcp-server

Pure-ESM Node.js MCP server with automatic tool discovery, Streamable HTTP and stdio transports, TLS, Zod schemas, injectable context, bearer authentication, and generic OAuth2 support.
Table of Contents
- Features
- Requirements
- Setup
- Usage
- Development
- Testing
- Troubleshooting
- Security
- API
- Packaging
- Examples
- Support
- Links
- License
Features
Create MCP servers with Streamable HTTP or stdio, discovered tool modules, Zod input schemas, shared context, and optional authentication.
Requirements
Use Node.js 26 or later. Use an MCP client that supports protocol revision 2026-07-28 and the selected transport.
Setup
Install the package with npm install @eliware/mcp-server. Read the setup guide before you create a server.
Usage
Create a server with mcpServer() and add tool modules in tools/. Read the usage guide, configuration guide, and authentication guide.
Browse the documentation index, specifications index, and release notes.
Tools
Add one .mjs module for each tool in tools/. Read the tool guide for registration and context details.
Resources
The package does not scan resource files. Add resources to the SDK server inside a tool module. Read the tool guide.
Prompts
The package does not scan prompt files. Add prompts to the SDK server inside a tool module. Read the tool guide.
Transport
Use Streamable HTTP or stdio. The package does not support HTTP with SSE. Read the protocol requirements.
Authentication
Select no authentication, a static bearer token, bearer passthrough, or OAuth2 introspection. Use HTTPS for OAuth endpoints. Read the authentication guide.
Schemas
Import z from @eliware/mcp-server to define tool input schemas. Read the tool guide.
Development
Run npm ci to install locked dependencies. Run npm run format to format files. Run npm run format:check to check file formatting.
Run npm run lint for lint checks. Run npm run audit for dependency checks. Run npm run typecheck to check TypeScript declarations.
Testing
Run npm test for aggregate validation. Run npm run pack to check package contents.
Troubleshooting
Read the troubleshooting guide for setup and runtime issues.
Security
Keep tokens, OAuth client secrets, and TLS keys in environment variables or secret files. Use HTTPS and explicit authentication for remote access.
API
Read the API reference for exports, options, and result types.
Packaging
The npm package includes src/, docs/, README.md, AGENTS.md, LICENSE, RELEASE_NOTES.md, examples/, specs/, and .env.example.
Use numeric MAJOR.MINOR.PATCH versions and a v<version> tag for each release. Run npm run pack to check package contents. The npm workflow publishes approved tagged releases.
Examples
Read examples/README.md for server and tool examples.
Support
For help, questions, or to chat with the author and community, visit:
Links
License
@eliware/mcp MCP questions
How do I add @eliware/mcp MCP to Claude Code?
Run claude mcp add mcp-server -- npx -y @eliware/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add @eliware/mcp MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What are the Node.js requirements?
You must use Node.js version 26 or later.
Does this server support HTTP with SSE?
No, the package supports Streamable HTTP and stdio, but it does not support HTTP with SSE.
How do I add tools to my server?
You can add tools by placing one .mjs module for each tool in the tools/ directory.
Can I use Zod for input schemas?
Yes, you can import z from @eliware/mcp-server to define tool input schemas.


