MCP.so
ログイン

FlowMCP Server MCP Server

@FlowMCP

基本情報

カテゴリ

その他

トランスポート

stdio

作者

FlowMCP

FlowMCP Server MCP Server について

Provides local and remote servers to run FlowMCP schemas via stdio or HTTP/SSE for AI–API integration.

FlowMCP Server MCP Server の設定

標準の設定はありません

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

リポジトリ

FlowMCP Server MCP Server のツール

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

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

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

概要

What is FlowMCP Server?

FlowMCP Server provides two server implementations for the FlowMCP framework: a LocalServer for local stdio-based execution and a RemoteServer for networked usage via HTTP and SSE. It is designed for developers building CLI tools, testing environments, frontend apps, and remote agents.

How to use FlowMCP Server?

Install the package (flowmcp-server), create a LocalServer or RemoteServer instance, prepare schema activations with FlowMCP.prepareActivations(...), add them via addActivationPayloads(...), then call start(). See the code examples in the README for local and remote configurations.

Key features of FlowMCP Server

  • Lightweight local server using stdin/stdout with no extra dependencies
  • Remote server supporting three transport protocols: SSE, stickyStreamable, statelessStreamable
  • Optional Bearer token authentication for remote endpoints
  • Configurable server metadata (name, description, version) via setConfig
  • Compatible with FlowMCP framework and SchemaImporter for schema activation

Use cases of FlowMCP Server

  • Run FlowMCP schemas locally in a CLI tool or development environment
  • Expose schemas over HTTP for remote AI agents or web frontends
  • Test schema activations with a simple local server before deploying
  • Serve multiple routes with different transport protocols and authentication

よくある質問

1

What transport protocols does the RemoteServer support?

It supports `sse` (Server-Sent Events), `stickyStreamable` (HTTP with reusable sessions), and `statelessStreamable` (stateless POST-based HTTP).

2

How do I enable authentication on the RemoteServer?

Set the `bearer` option when calling `addActivationPayloads()`. Incoming requests must then include the header `Authorization: Bearer <TOKEN>`. Missing or invalid tokens return 401 or 403.

3

Can I customize the server name, description, or version?

Yes. Use `localServer.setConfig({ overwrite: { serverDescription: { name, description, version } } })` or the equivalent on RemoteServer.

4

What version of FlowMCP Server is required?

FlowMCP Server version `1.2.0+` is required, and it works with FlowMCP Schema spec version `1.2.2` (as shown in the example).

5

Where does the data (schemas) come from?

Schemas are imported using the `SchemaImporter` package, which fetches them with `SchemaImporter.get({ withSchema: true })`. The README does not specify storage location.

コメント

「その他」の他のコンテンツ