Lite_MCP_sdk

MCP开发工具

提供方 S2thend

开发工具 未标注 OAuth 授权 社区 / 第三方 ClaudeCursorCodexZed

a light weight version of mcp sdk inspired by official model context protocol sdk, NOW focus on sse only no stdio

一句话选型结论

按资料字段整理

Lite_MCP_sdk 属于开发工具类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude、Cursor、Codex 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

javascriptagentmcp

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Lite_MCP_sdk当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方S2thend上游标注的维护方 S2thend
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

10.2 KB
来自项目仓库与上游目录的原文,未做删改

Introduction

This repo now includes 2 parts:
1. Lite mcp sdk for javascript
2. Lite mcp for javascript

Project Goal

The goal of this project is to make best of the AI Agent tech available to any Grandma👵 who learned 5 minutes of javascript.

Why javascript?

Because I want the project to condense on the running logics, rather than distracted by the types.

Lite mcp for javascript Introduction

Lite mcp for javascript is the BEST yet way to start a REMOTE SSE
javascript MCP server and Client.

🚀 Quick start

REAL COPY AND PASTE experince for you to get started with MCP.

Installation```bash

npm install litemcpjs
npm install express
npm install cors


### Build a SSE MCP client under 5 lines```javascript
import { MCPClient } from "litemcpjs";

async function main() {
  const client = new MCPClient("http://localhost:3000") // change this to your server url
  await client.connect()
  await client.listTools()
  const result = await client.callTool("calculate-bmi", {weightKg: 70, heightM: 1.75})
  console.log(result)
}

main();

Start a REMOTE MCP SSE server with expressJS```javascript

const { MCPServerInit } = require("litemcpjs");

// define the tools
const TOOLS = [
{
name: "calculate-bmi",
description: "Calculate the BMI of a person",
inputSchema: {
type: "object",
properties: {
weightKg: { type: "number" },
heightM: { type: "number" },
},
required: ["weightKg", "heightM"],
},
method: async ({ weightKg, heightM }) => {
return {
content: [{
type: "text",
text: String(weightKg / (heightM * heightM))
}]
}
}
}
];

// define extra handlers for resources etc.
const handlers = {};

// compatible for server have .use(middleware) method such as express
const middlewares = [
cors(),
];

const MCPapp = express();

const MCPServer = MCPServerInit(
MCPapp,
middlewares,
handlers,
TOOLS,
).listen(5556);


## Lite mcp sdk for javascript Introduction

For Anyone wants a little **more low level control** over the MCP protocol:

Lite mcp sdk for javascript is a lightweight mcp sdk **remix** with minimal dependencies.

### Quick start```bash
npm install lite-mcp-sdk

Server```javascript

const { Server, SSEServerTransport } = require("lite-mcp-sdk");

//or module import
import { Server, SSEServerTransport } from "lite-mcp-sdk";

//create a server
const server = new Server({
port: 3000,
transport: new SSEServerTransport(),
});

// 1. Define the server info
const server = new Server({
name: "example-servers/puppeteer",
version: "0.1.0",
}, {
capabilities: {
resources: {},
tools: {},
},
});

// 2. Define the request handlers
server.setRequestHandler("tools/call", async (request) => {
const { name, arguments: args } = request.params;
return handleToolCall(name, args);
});

//3. Define the transport
const transports = new Map();
const transport = new SSEServerTransport("/messages", res);
transports.set(clientId, transport);

//4. Connect the server to the transport
await server.connect(transport);

//5. Handle the post message
await transport.handlePostMessage(req, res);


### Client```javascript
import { Client, SSEClientTransport } from "lite-mcp-sdk";

// 1. Define the client
let client = new Client( {
      name: "fastmcp-client",
      version: "0.1.0"
    }, {
      capabilities: {
        sampling: {},
        roots: {
          listChanged: true,
        },
      },
    } );

// 2. Init the client transport
const serverUrl = "http://localhost:3000"; // for example

const backendUrl = new URL(`${serverUrl}/sse`);

backendUrl.searchParams.append("transportType", "sse");

backendUrl.searchParams.append("url", `${serverUrl}/sse`);

const headers = {};

const clientTransport = new SSEClientTransport(backendUrl, {
    eventSourceInit: {
        fetch: (url, init) => fetch(url, { ...init, headers }),
    },
    requestInit: {
        headers,
    },
});

// 3. Connect the client to the transport
await client.connect(clientTransport);
const abortController = new AbortController();
let progressTokenRef = 0;

// 4. start the tool call
const name = "toolcall name";
const params = {}; // tool call params

const response = await client.request(
    {
          method: "tools/call",
          params: {
            name,
            arguments: params,
            _meta: {
              progressToken: progressTokenRef++,
            },
          },
    },
    {signal: abortController.signal,}
);

Project structure:

The project is clearly and cleanlyorganized into the following directories:```shell
src
├── index.js
└── lib
├── client
│ ├── client.js
│ └── clientTransport.js
├── server
│ ├── server.js
│ └── serverTransport.js
└── shared
├── helpers
│ ├── constants.js
│ └── util.js
├── protocol.js
└── validators
├── capabilityValidators.js
└── schemaValidators.js (IN CONSTRUCTION)

## Why choose lite-mcp-sdk?

### 1. No fixed zod types
NO More zod types!!! zod types contributes to unneccessary complexity for easy setups.

Furthermore, the way zod type is used in the original sdk is rigid and not flexible, and it is an well received issue.

### 2. Fully SSE solution

Focus on **SSE**, and removed stdio support for simplicity considerations, since it is not a as univerial solution as SSE.

Suprisingly, the SSE solution is scarce on the internet, so I decided to write my own.

BELOW images shows that stdio support is always descripted, but no SSE support is mentioned.

Even when you search deliberately for SSE, result is scarce, SEE for first page google results.

Replace codes like requestSchema.parse to fully customizable validators and hand it over to the user to define the validation logic here. e.g.```javascript
const validatedMessage = validator(message);

How timeout is used in original sdk is vague and has some redundant implementations,which are removed in lite mcp for not causing further confusion.(Ok I think they also removed these in latest version)

3. More detailed documentation on how to quickly get started

They actually listed this problem in the official roadmap. lol

Lite MCP SDK provides better documentation on how to use and modify the sdk, with more ready to copy code examples.

4. Cleaner architecthure with only core functionalities

Lite MCP SDK:```shell
src
├── index.js
└── lib
├── client
│ ├── client.js
│ └── clientTransport.js
├── server
│ ├── server.js
│ └── serverTransport.js
└── shared
├── helpers
│ ├── constants.js
│ └── util.js
├── protocol.js
└── validators
├── capabilityValidators.js
└── schemaValidators.js (IN CONSTRUCTION)

Official sdk:
Although it is listed on the roadmap, I think putting auth in this project is poor product design.

Honestly I think left users to handle auth problem provides more flexibility and better dev experience.```shell
src/
├── client
│   ├── auth.test.ts
│   ├── auth.ts
│   ├── cross-spawn.test.ts
│   ├── index.test.ts
│   ├── index.ts
│   ├── sse.test.ts
│   ├── sse.ts
│   ├── stdio.test.ts
│   ├── stdio.ts
│   └── websocket.ts
├── cli.ts
├── inMemory.test.ts
├── inMemory.ts
├── integration-tests
│   └── process-cleanup.test.ts
├── server
│   ├── auth
│   │   ├── clients.ts
│   │   ├── errors.ts
│   │   ├── handlers
│   │   │   ├── authorize.test.ts
│   │   │   ├── authorize.ts
│   │   │   ├── metadata.test.ts
│   │   │   ├── metadata.ts
│   │   │   ├── register.test.ts
│   │   │   ├── register.ts
│   │   │   ├── revoke.test.ts
│   │   │   ├── revoke.ts
│   │   │   ├── token.test.ts
│   │   │   └── token.ts
│   │   ├── middleware
│   │   │   ├── allowedMethods.test.ts
│   │   │   ├── allowedMethods.ts
│   │   │   ├── bearerAuth.test.ts
│   │   │   ├── bearerAuth.ts
│   │   │   ├── clientAuth.test.ts
│   │   │   └── clientAuth.ts
│   │   ├── provider.ts
│   │   ├── router.test.ts
│   │   ├── router.ts
│   │   └── types.ts
│   ├── completable.test.ts
│   ├── completable.ts
│   ├── index.test.ts
│   ├── index.ts
│   ├── mcp.test.ts
│   ├── mcp.ts
│   ├── sse.ts
│   ├── stdio.test.ts
│   └── stdio.ts
├── shared
│   ├── auth.ts
│   ├── protocol.test.ts
│   ├── protocol.ts
│   ├── stdio.test.ts
│   ├── stdio.ts
│   ├── transport.ts
│   ├── uriTemplate.test.ts
│   └── uriTemplate.ts
└── types.ts

Key Difference Table

Feature mcp-official-sdk lite-mcp-sdk
Validation zod Validators
Transport stdio or SSE SSE only
Language typescript javascript
Auth included optional
Documentation vague clear
Architecture complex lightweight

🗺️ Roadmap

  • [ ] Custom Validators (under construction)
  • [ ] Add dashboard for monitoring and managing the MCP server and client
  • [ ] Add ts types
  • [ ] Add python sdk

🤝 Contributing

Contributions are welcome! Please open an issue or submit a pull request.

Please read the contributing document.

📝 Licensing

This project is licensed under the MIT License. See the LICENSE file for details.

Inspired by Original anthropic sdk,which license is also included here.

Contact

If you have any questions or suggestions, please leave a comment here.
Or contact me via email: borui_cai@qq.com

Projects using lite-mcp-sdk (to add)

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Lite_MCP_sdk 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Lite_MCP_sdk 怎么在 Claude、Cursor、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Lite_MCP_sdk 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Lite_MCP_sdk 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Lite_MCP_sdk 支持哪些客户端?

资料标注支持 Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Lite_MCP_sdk 能提供哪些能力?

资料显示能力标签包括 javascript、agent、mcp、openai、function calling、agentic ai。具体工具清单以官方文档为准。

Lite_MCP_sdk 需要什么运行环境?

运行时为 node。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。