agentleFS
The-Artificer-of-Ciphers-LLCThe-Artificer-of-Ciphers-LLC/skills-from-the-artificer/swift-mcp-server-generator/SKILL.md

swift-mcp-server-generator

Skill6 starsChanged 34 days agoMITView on GitHub

Generate a complete Model Context Protocol server project in Swift using the official MCP Swift SDK package.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked to create a Swift MCP server, work through this list and tick each item as it is done:

    line 12
  2. Distinctive:

    If the user wants something the templates do not cover, adapt the closest template rather than inventing a different project shape.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swift MCP Server Generator

Generate a complete, production-ready MCP server in Swift using the official Swift SDK package.

Generation checklist

When asked to create a Swift MCP server, work through this list and tick each item as it is done:

  • Ask for the project name and a one-line description
  • Generate every file in the structure below from references/templates.md, renaming MyMCPServer throughout (drop the Resources/ or Prompts/ group only if the user says the server does not need it)
  • Shared state lives in actors; async/await throughout, no completion handlers
  • swift-log logging and ServiceLifecycle graceful shutdown wired in main.swift
  • Errors surfaced as MCPError; public APIs carry doc comments; Swift naming conventions (camelCase / PascalCase)
  • A test per handler in ServerTests.swift
  • swift build and swift test run clean before handing over; report their output

If the user wants something the templates do not cover, adapt the closest template rather than inventing a different project shape.

Project structure

Generate the complete project with this layout:

my-mcp-server/
├── Package.swift
├── Sources/
│   └── MyMCPServer/
│       ├── main.swift
│       ├── Server.swift
│       ├── Tools/
│       │   ├── ToolDefinitions.swift
│       │   └── ToolHandlers.swift
│       ├── Resources/
│       │   ├── ResourceDefinitions.swift
│       │   └── ResourceHandlers.swift
│       └── Prompts/
│           ├── PromptDefinitions.swift
│           └── PromptHandlers.swift
├── Tests/
│   └── MyMCPServerTests/
│       └── ServerTests.swift
└── README.md

Templates

Each file has a complete template in references/templates.md. Read only the sections you need:

FileSection in references/templates.md
Package.swiftPackage.swift Template
Sources/MyMCPServer/main.swiftmain.swift Template
Sources/MyMCPServer/Server.swiftServer.swift Template
Sources/MyMCPServer/Tools/ToolDefinitions.swiftToolDefinitions.swift Template
Sources/MyMCPServer/Tools/ToolHandlers.swiftToolHandlers.swift Template
Sources/MyMCPServer/Resources/ResourceDefinitions.swiftResourceDefinitions.swift Template
Sources/MyMCPServer/Resources/ResourceHandlers.swiftResourceHandlers.swift Template
Sources/MyMCPServer/Prompts/PromptDefinitions.swiftPromptDefinitions.swift Template
Sources/MyMCPServer/Prompts/PromptHandlers.swiftPromptHandlers.swift Template
Tests/MyMCPServerTests/ServerTests.swiftServerTests.swift Template
README.mdREADME.md Template

Build and Run

# Build
swift build

# Run
swift run

# Test
swift test

# Release build
swift build -c release

# Install
swift build -c release
cp .build/release/MyMCPServer /usr/local/bin/

Integration with Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "my-mcp-server": {
      "command": "/path/to/MyMCPServer"
    }
  }
}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.