Server E347bb17

MCP开发工具

提供方 mcp-z

开发工具 未标注 无需鉴权 社区 / 第三方

提供构建MCP服务器的共享工具,包括传输配置、中间件组合和文件服务功能,适用于需要快速搭建和扩展服务器的开发场景。

一句话选型结论

按资料字段整理

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

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

工具与能力

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

能力标签

适用场景

服务器构建TypeScript本地部署中间件组合文件服务传输配置开发工具

安装与配置

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

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

本地命令与脚本

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

接口联调与测试

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

选择建议

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

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Server E347bb17当前 未标注 未标注 未标注 无 2026-05-17
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

服务器档案

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

详细介绍

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

@mcp-z/server

Shared utilities and server orchestration for building MCP (Model Context Protocol) servers

Common uses

  • Parse transport config for stdio or HTTP
  • Wire MCP servers to stdio or Express HTTP
  • Compose auth/logging middleware
  • Serve generated files (PDFs, CSVs)
  • Build field/pagination/shape schemas

Install```bash

npm install @mcp-z/server @modelcontextprotocol/server express


The example imports the MCP SDK and Express directly, so they are explicit application dependencies.

## Quick start```ts
import express from 'express';
import { McpServer } from '@modelcontextprotocol/server';
import { parseConfig, connectStdio, connectHttp } from '@mcp-z/server';

const config = parseConfig(process.argv.slice(2), process.env);
const writeLog = (...args: unknown[]) => console.error(...args);
const logger = { debug: writeLog, info: writeLog, warn: writeLog, error: writeLog };
const buildServer = () => {
  const server = new McpServer({ name: 'my-server', version: '1.0.0' });
  server.registerTool('hello', { description: 'Return a greeting' }, async () => ({
    content: [{ type: 'text', text: 'Hello from my server' }]
  }));
  return server;
};

if (config.transport.type === 'stdio') {
  await connectStdio(buildServer, { logger });
} else {
  const app = express();
  await connectHttp(buildServer, { logger, app, port: config.transport.port });
}

Keep logs on stderr. Writing logs to stdout corrupts the stdio protocol stream.

Protocol versions

connectHttp and connectStdio serve both the 2025 and 2026-07-28 MCP protocol revisions from
the same server definitions, on the same HTTP endpoint and the same stdio connection. A legacy
2025 client keeps working unchanged; support for it is not being dropped.

Serving both revisions requires a factory, not an McpServer instance. The 2026-07-28
revision is stateless. A client speaking it sends no initialize handshake, and the SDK caches
the negotiated revision on the McpServer instance. Its own documentation puts it plainly: once a
version is negotiated, "a negotiated session never re-routes a method onto the other era." So a
single shared instance pins itself to whichever revision reaches it first and answers the other
with -32601 Method not found. A factory hands every request (HTTP) or connection (stdio) a
fresh, un-negotiated instance, so each one negotiates for itself:```ts
const buildServer = () => {
const mcpServer = new McpServer({ name: 'my-server', version: '1.0.0' });
// register tools/resources/prompts on mcpServer
return mcpServer;
};

await connectStdio(buildServer, { logger });
// or
await connectHttp(buildServer, { logger, app, port: config.transport.port });


Passing a ready-made `McpServer` instance is still accepted and still compiles, but it is correct only
for a server that will speak **one** revision.
If both eras must work, pass a factory. A factory serves 2025-era clients exactly as an instance
did, so there is no reason to prefer an instance once you have one.

## Cache hints

On 2026-07-28 the SDK stamps `ttlMs` and `cacheScope` onto every cacheable result, defaulting to
`ttlMs: 0` / `cacheScope: 'private'`. This safe default disables caching.
`defaultCacheHints` is a policy for a typical mcp-z server: catalogs are cacheable and shareable,
anything derived from a user's account is not.```ts
import { McpServer } from '@modelcontextprotocol/server';
import { defaultCacheHints } from '@mcp-z/server';

const mcpServer = new McpServer({ name: 'my-server', version: '1.0.0' }, { cacheHints: defaultCacheHints });

tools/list, prompts/list, resources/templates/list and server/discover are given a five-minute
TTL and cacheScope: 'public', because each is fixed at registration and identical for every caller.
resources/list and resources/read stay private with no TTL: those vary by account, and marking
them public would let a shared cache serve one user's data to another. Override a single operation
by spreading ({ ...defaultCacheHints, 'tools/list': { ttlMs: 0 } }). 2025-era responses are
unaffected because the fields do not exist there.

Registration helpers

  • registerTools(server, tools)
  • registerResources(server, resources)
  • registerPrompts(server, prompts)

Each registers in name order, not the order the array happened to arrive in, so two servers built
from the same modules produce identical tools/list results. That is what lets a 2026-07-28 client
keep a cached catalog valid across a reconnect. The array you pass is not mutated.

Middleware composition

Use composeMiddleware with middleware layers (auth, logging, etc.):```ts
import { composeMiddleware, createLoggingMiddleware } from '@mcp-z/server';

const logging = createLoggingMiddleware({ logger });
const composed = composeMiddleware({ tools, resources, prompts }, [
{ withTool: authMiddleware.withToolAuth, withResource: authMiddleware.withResourceAuth, withPrompt: authMiddleware.withPromptAuth },
{ withTool: logging.withToolLogging, withResource: logging.withResourceLogging, withPrompt: logging.withPromptLogging }
]);


## File serving utilities

For servers that generate files (PDFs, CSVs, images):

- `reserveFile()` - Reserve a file path for streaming writes
- `writeFile()` - Write a buffer directly
- `getFileUri()` - `file://` or `http://` URI based on transport
- `createFileServingRouter()` - Express router to serve files```ts
import { reserveFile, getFileUri, createFileServingRouter } from '@mcp-z/server';

const reservation = await reserveFile('report.csv', { resourceStoreUri: 'file:///tmp/files' });
const uri = getFileUri(reservation.storedName, transport, {
  resourceStoreUri: 'file:///tmp/files',
  baseUrl: 'https://example.com',
  endpoint: '/files'
});

const router = createFileServingRouter({ resourceStoreUri: 'file:///tmp/files' }, { contentType: 'text/csv' });
app.use('/files', router);

Schema helpers

Helpers for consistent tool inputs and output shaping:

  • createFieldsSchema() / parseFields() / filterFields()
  • createPaginationSchema()
  • createShapeSchema() / toColumnarFormat()

Requirements

  • Node.js >= 20

Documentation

API Docs

常见问题

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

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

Server E347bb17 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Server E347bb17 收费吗?

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

Server E347bb17 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Server E347bb17 能提供哪些能力?

资料显示能力标签包括 服务器构建、TypeScript、开发工具。具体工具清单以官方文档为准。

热门专题

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

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