Mcpservers B9e19bb0

MCPAI代理

提供方 AGenNext

AI代理 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude DesktopClaude
查看接入方式

MCPHub是一个Model Context Protocol服务器注册中心,提供58个服务器和1000多种工具,支持独立构建、运行、打包和部署。

一句话选型结论

按资料字段整理

Mcpservers B9e19bb0 属于AI代理类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude Desktop、Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

服务器注册TypeScript本地部署Node.js工作区独立部署Docker支持MCP协议

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
docker run -d \

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Docker,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Mcpservers B9e19bb0当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方AGenNext上游标注的维护方 AGenNext
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Docker本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

Agent-Tools

Agent-Tools is the canonical tool catalog for the AGenNext platform.

This is a cloud marketplace-style catalog problem.

A tool is an invocable catalog object that can be discovered, governed, versioned, permissioned, reviewed, priced, installed, and used by agents, workflows, teams, and runtimes.

Core model```text

Tool
= primary catalog object
= invocable capability/product

Tool metadata includes:
- capabilities
- author
- publisher
- versions
- provider offers
- license
- pricing
- risk
- approval requirements
- invocation contracts


The primary catalog object is always the **Tool**.

Capability, author, publisher, version, and provider are metadata attached to the tool record.

## Role definitions```text
Capability
  = standardized semantic ability implemented by the tool

Author
  = creator or maintainer of the tool

Publisher
  = party that lists, curates, verifies, or publishes the tool into the catalog

Version
  = version metadata and compatibility contract for the tool

Provider Offer
  = one access path for a specific tool version

Provider
  = organization, package, service, MCP server, CLI, SDK, HTTP API, marketplace, or runtime endpoint offering that version

Marketplace rule```text

One Tool
can implement many Capabilities

One Tool
can have many Versions

One Tool Version
can have many Provider Offers

One Provider
can offer many Tools

One open-source Tool
can have many Providers

One MCP Server
is a Provider type

One MCP Server
can expose many Tools


## Example: tool with capability, author, publisher, version, and providers```yaml
id: filesystem.read_file
type: tool
name: Read File

capabilities:
  - file.read

author:
  name: AGenNext
  type: Organization

publisher:
  name: AGenNext
  type: Organization

versions:
  - version: 1.0.0
    status: active
    contract:
      inputs:
        path: string
      outputs:
        content: string
    providers:
      - provider_id: filesystem-mcp-server
        provider_type: mcp_server
        protocol: mcp
        package_path: packages/filesystem-mcp-server
        offer_status: active

      - provider_id: internal-filesystem-http
        provider_type: http_api
        protocol: https
        offer_status: active

risk: medium
approval_required: false

Example: open-source tool with multiple providers```yaml

id: surrealkit
type: tool
name: SurrealKit

capabilities:
- database.schema.generate
- database.migration.run
- database.seed.load

author:
name: SurrealDB
type: Organization

publisher:
name: AGenNext
type: Organization
role: catalog_curator

versions:
- version: 2.2.1
status: supported
providers:
- provider_id: surrealkit-github-release
provider_type: github_release
install_strategy: pinned_binary
version_policy: pinned

  - provider_id: surrealkit-npm
    provider_type: npm_package
    install_strategy: package_manager
    version_policy: pinned

  - provider_id: agennext-ci-wrapper
    provider_type: ci_wrapper
    install_strategy: workflow_script
    version_policy: pinned

## Repository responsibilities

Agent-Tools owns:```text
- tool catalog entries
- capability references used by tools
- author and publisher metadata
- version metadata and compatibility contracts
- provider offer metadata
- external tool definitions
- MCP provider/package metadata where needed
- tool invocation contracts
- tool security, approval, pricing, and governance metadata

Agent-Tools does not own:```text
- runtime execution of agents
- skill definitions
- agent blueprints
- graph schema
- grammar rules
- seed-data ownership


## Current folders

### `catalog/`

Canonical catalog entries for tools and external tools.

Example:```text
catalog/surrealkit.tool.yaml

Each file should describe a tool first.

Capabilities, author, publisher, versions, and provider offers belong inside the tool entry as metadata.

packages/

Existing folders under packages/ are provider implementation packages.

Most current packages are MCP server implementations. They should be migrated conceptually from:```text
MCP server = catalog item


to:```text
Tool = catalog item
MCP server = provider offer metadata under a tool version

Recommended package structure:```text
packages/<provider-name>/
provider.yaml # provider/package metadata
tools/ # tool catalog entries exposed through this provider
<tool-id>.tool.yaml
src/ # provider implementation
package.json
tsconfig.json


## MCP provider model

An MCP server package should declare which tools it provides:```yaml
provider_id: filesystem-mcp-server
provider_type: mcp_server
provides:
  - tool_id: filesystem.read_file
    version: 1.0.0
  - tool_id: filesystem.write_file
    version: 1.0.0
  - tool_id: filesystem.list_directory
    version: 1.0.0

Each exposed tool should have a catalog entry with provider offer metadata:```yaml
id: filesystem.read_file
type: tool
capabilities:
- file.read
versions:
- version: 1.0.0
providers:
- provider_id: filesystem-mcp-server
provider_type: mcp_server
protocol: mcp
risk: medium
approval_required: false


## Capability standardization

Capabilities should be stable semantic identifiers.

Examples:```text
file.read
file.write
filesystem.list
database.query
database.schema.generate
database.migration.run
database.seed.load
cloud.compute.create
cloud.storage.object.read

Capabilities allow the platform to compare tools, substitute providers, reason about risk, and match skills to tools.

Build existing provider packages

Existing packages can still be built as Node.js workspaces:```bash
npm install
npm run build
npm run build:changed
npm run build --workspace=packages/<provider-name>


Run a built MCP provider directly:```bash
node packages/&lt;provider-name&gt;/dist/index.js

Environment variables

Provider packages may require credentials or service URLs.

Common examples:```bash
SERVICE_URL="https://your-service.com"
SERVICE_API_KEY="your-api-key"
ALLOWED_DIRECTORIES="/data"


Never commit secrets into this repository. Use environment variables, Docker secrets, or runtime secret stores.

## Migration rule for existing packages

Do not delete existing provider packages immediately.

Migrate them in place:```text
1. Identify the tools exposed by each provider package.
2. Identify capabilities implemented by each tool.
3. Add one .tool.yaml catalog entry per tool.
4. Add capability, author, publisher, and version metadata under each tool.
5. Add provider offers under each version.
6. Add provider.yaml only for package/build/runtime metadata.
7. Mark tool risk, approval requirements, auth, pricing, license, and support metadata where known.
8. Keep implementation under src/.
9. Build and test provider package.

Relationship to other repos```text

Agent-Skills
uses tools as executable capabilities

Agent-Graph
maps tools, capabilities, authors, publishers, versions, providers, permissions, and invocations

Agent-Grammar
validates tool metadata

Agent-Seed
seeds default platform tool records

Agent-Review
reviews high-risk tools before publication/use


## Rule```text
Tool
  = primary catalog object

Capability
  = semantic ability metadata

Author
  = creator/maintainer metadata

Publisher
  = catalog publishing/curation metadata

Version
  = compatibility metadata

Provider Offer
  = access path metadata for a version

常见问题

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

在客户端按下面的安装命令接入:docker run -d \。装完在客户端配置里引用同一个包或端点。

Mcpservers B9e19bb0 怎么在 Claude Desktop、Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Mcpservers B9e19bb0 收费吗?

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

Mcpservers B9e19bb0 需要 API Key 吗?

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

Mcpservers B9e19bb0 支持哪些客户端?

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

Mcpservers B9e19bb0 能提供哪些能力?

资料显示能力标签包括 TypeScript、Claude、Docker支持。具体工具清单以官方文档为准。

Mcpservers B9e19bb0 需要什么运行环境?

运行时为 Docker;属于本地进程,需要在本机装好运行环境。

Mcpservers B9e19bb0 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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