MCP.so
ログイン

Nest Llm Aigent MCP Server

@luis1232023

基本情報

カテゴリ

AI とエージェント

トランスポート

stdio

作者

luis1232023

Nest Llm Aigent MCP Server について

Stdio Mcp Server 转为 RestFul,轻松部署与 Web 服务集成, mcp gateway

Nest Llm Aigent MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Nest Llm Aigent MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Nest Llm Aigent?

Nest Llm Aigent is a forwarding/proxy solution that wraps multiple MCP (Model Context Protocol) servers into a unified HTTP service for large language models. Designed for developers integrating MCP capabilities into existing web services (e.g., NestJS), it acts as an AI agent that centralizes configuration and exposes standardized RESTful endpoints.

How to use Nest Llm Aigent?

Install MCP servers as private NPM packages and configure them in an mcp.config.json file. The running service exposes POST endpoints at paths like /api/mcp/tools, /api/mcp/tools/call, and /api/mcp/agent for HTTP-based access to tools, resources, and LLM invocation.

Key features of Nest Llm Aigent

  • Acts as an AI agent aggregating multiple MCP servers
  • Exposes standardized HTTP RESTful API endpoints
  • Supports nearly all large language models
  • MCP servers deployed as private NPM packages
  • Centralized configuration via mcp.config.json
  • Returns OpenAI-compatible function call definitions

Use cases of Nest Llm Aigent

  • Integrate MCP tools into existing NestJS web services
  • Centrally manage and version control multiple MCP servers
  • Provide HTTP-based LLM access to non-MCP applications
  • Unify tool, resource, and prompt retrieval in one service

よくある質問

1

What transport protocol does Nest Llm Aigent use for MCP servers?

Currently only stdio transport is implemented; SSE server support is planned for future versions.

2

How are MCP servers deployed and configured?

MCP servers are packaged as private NPM packages, installed via `npm install`, and configured in a `mcp.config.json` file defining server path, arguments, and name.

3

What endpoints does Nest Llm Aigent expose?

POST endpoints at `/api/mcp/tools`, `/api/mcp/functools`, `/api/mcp/tools/call`, `/api/mcp/resources`, `/api/mcp/prompts`, `/api/mcp/all`, and `/api/mcp/agent`.

4

Does Nest Llm Aigent support all large language models?

Yes, the project aims to support nearly all large model invocations through its HTTP API.

5

Where does tool execution happen?

Nest Llm Aigent is a forwarding layer; actual tool execution occurs in the connected MCP servers, which it bridges to HTTP requests.

コメント

「AI とエージェント」の他のコンテンツ