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.

评论

其他 分类下的更多 MCP 服务器