広告掲載
MCP.so
ログイン

MCP Core Library

@MCPStudio

リポジトリ

基本情報

カテゴリ

開発者ツール

ライセンス

MIT license

トランスポート

stdio

作者

MCPStudio

MCP Core Library について

Contains the business logic and MCP server ports.

#mcp-core#business-logic#hexagonal-architecture

MCP Core Library の設定

標準の設定はありません

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

リポジトリ

MCP Core Library のツール

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

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

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

概要

What is MCP Core Library?

MCP Core Library is a crate containing the domain business logic and ports of an MCP server, following a hexagonal architecture. It defines pure business logic and interfaces (ports) while remaining independent of implementation details and specific technologies.

How to use MCP Core Library?

The README does not include installation or configuration instructions. It describes the crate’s architectural role and components; usage details would be provided in the crate’s own documentation.

Key features of MCP Core Library

  • Contains only domain business logic and ports.
  • Defines a Tool port for executable tools.
  • Defines a Transport port for network communication.
  • Includes abstract message types and domain errors.
  • Uses ToolRegistry for registering and searching tools.
  • Minimal dependencies: serde and tokio only.

Use cases of MCP Core Library

  • Building an MCP server with clean hexagonal architecture.
  • Decoupling domain logic from implementation details like JSON-RPC.
  • Managing tool registration and execution via ToolRegistry.

よくある質問

1

What is the purpose of the MCP Core Library?

It holds the domain business logic and ports of an MCP server, following hexagonal architecture to keep domain independent of technology.

2

What dependencies does it require?

Only basic crates: `serde` and `tokio` (for async types), to remain minimal and preserve domain isolation.

3

Does it handle serialization protocols like JSON-RPC?

No, specific protocol details like JSON-RPC are deliberately excluded and will be implemented in external adapters, in accordance with hexagonal architecture principles.

4

How are tools managed in the library?

The `ToolRegistry` provides registration and search of tools by name. A simple internal implementation uses a `HashMap<String, Box<dyn Tool>>`, but could be formalized as a trait for different storage strategies.

5

What are the main ports defined?

Primary/driving ports: `Tool` (interface for executable tools). Secondary/driven ports: `Transport` (interface for network communication).

コメント

「開発者ツール」の他のコンテンツ

Capgo MCP

Cap-go

Console, Backend and CLI to manage Capgo Instant update and Native build for Capacitor apps Build and upload to app store your mobile app

Eddyter AI Rich Text Editor MCP

EddyterAI

Set up and manage the Eddyter AI rich text editor by talking to your AI agent — for Claude, Cursor, Codex and other MCP tools. A Model Context Protocol server that lets AI tools add Eddyter to a React, Next.js, Vite or R

9

TranscriptFetch MCP Server

TranscriptFetch

Model Context Protocol (MCP) server for TranscriptFetch: fetch YouTube transcripts, search, channels, and playlists from any MCP client.

Crawl Readiness

Grubbomatic

AI SEO tools for MCP clients — audit whether AI crawlers can read a website, validate JSON-LD and robots.txt, and generate llms.txt, AI-crawler-aware robots.txt, and JSON-LD schema without leaving the conversation.

Casefile

azimov777

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

3
広告掲載