MCP.so
ログイン

SwiftMCP MCP Server

@Cocoanetics

基本情報

カテゴリ

その他

ライセンス

BSD-2-Clause

トランスポート

stdio

作者

Cocoanetics

投稿者

Oliver Drobnik

SwiftMCP MCP Server について

Model Context Protocol Server for Swift

SwiftMCP MCP Server の設定

標準の設定はありません

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

リポジトリ

SwiftMCP MCP Server のツール

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

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

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

概要

What is SwiftMCP?

SwiftMCP is a Swift implementation of the Model Context Protocol (MCP) for JSON-RPC communication over multiple transports. It is intended for Swift developers who want to build MCP servers or clients that expose tools, resources, and prompts to AI models and other MCP-aware applications.

How to use SwiftMCP?

Add SwiftMCP as a dependency in your Package.swift, then declare a server with the @MCPServer macro, define tools with @MCPTool, and configure a transport such as stdio, HTTP+SSE, or TCP+Bonjour. The included demo provides commands like SwiftMCPDemo stdio and SwiftMCPDemo httpsse --port 8080.

Key features of SwiftMCP

  • Multiple transport options: stdio, HTTP+SSE, TCP+Bonjour
  • JSON-RPC 2.0 compliance with OpenAPI generation
  • Built-in authorization and optional OAuth validation
  • Macros for tools (@MCPTool), resources (@MCPResource), and prompts (@MCPPrompt)
  • Typed client proxy generation for any MCP server
  • Cross-platform support (macOS, Linux, Windows via trait selection)

Use cases of SwiftMCP

  • Building a command‑line MCP server that communicates via stdin/stdout
  • Exposing server tools over HTTP with Server‑Sent Events for web clients
  • Creating a locally discoverable server using TCP+Bonjour for LAN environments
  • Generating a typed Swift client proxy from any MCP server’s tool schema
  • Adding OAuth‑protected endpoints that integrate with AI plugin manifests

よくある質問

1

What transports does SwiftMCP support?

SwiftMCP supports Standard I/O (stdio), HTTP+SSE (Server‑Sent Events), and TCP+Bonjour for local discovery. These can even be run in parallel.

2

How does authorization work in SwiftMCP?

The HTTP+SSE transport can require a bearer token via the `--token` option, or validate tokens through an OAuth provider using introspection or JWKS. Custom authorization handlers can also be set.

3

Can I generate a typed client proxy from any MCP server?

Yes. The `SwiftMCPUtility generate-proxy` command creates a typed Swift proxy from any MCP server (including non‑SwiftMCP servers) by inspecting its tool schemas. Optionally, return types can be enriched from an OpenAPI document.

4

Does SwiftMCP support OpenAPI integration?

When the `--openapi` option is enabled, the server exposes an OpenAPI specification at `/openapi.json` and an AI plugin manifest at `/.well-known/ai-plugin.json`, enabling integration with AI models that understand OpenAPI.

5

What are the platform requirements for SwiftMCP?

SwiftMCP is written in Swift and works on macOS, Linux, and Windows. By disabling the `Server` trait (which drops swift‑nio), the package builds on Windows and reduces dependencies for client‑only consumers.

コメント

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