Skip to content

borghei/Claude-Skills / engineering/mcp-server-builder

mcp-server-builder

Verified

Builds MCP servers: OpenAPI-to-tool conversion, tool and schema linting, TypeScript or Python scaffolds, transports. Use when exposing an API to AI agents, building a tool server, or reviewing MCP tool definitions.

references/transport-and-deployment.md

View on GitHub
# Transport and Deployment

Read this when choosing a transport, wiring a server into a client, and managing tool versions across releases.

## Choosing a Transport

| Transport | Use for | Notes |
|-----------|---------|-------|
| stdio | Local tools launched by the client (CLI, desktop) | Simplest; no network, no auth; one client per process |
| Streamable HTTP | Remote and shared servers | The current spec's HTTP transport: one endpoint (conventionally `/mcp`) for POST requests, with optional streamed responses; put auth in front of it |
| HTTP+SSE | Legacy clients only | Replaced by Streamable HTTP in the 2025 spec revisions; keep only for backward compatibility |

Default to stdio for local tools and Streamable HTTP for anything remote. Check the SDK version you install for the exact transport class names.

## Client Configuration

### Claude Code (project `.mcp.json`)

```json
{
  "mcpServers": {
    "project-tools": {
      "command": "node",
      "args": ["dist/index.js"],
      "env": {
        "PROJECT_ROOT": "/path/to/project",
        "DATABASE_URL": "${DATABASE_URL}"
      }
    },
    "remote-api-tools": {
      "type": "http",
      "url": "https://mcp.mycompany.com/mcp",
      "headers": {
        "Authorization": "Bearer ${MCP_API_TOKEN}"
      }
    }
  }
}
```

Claude Desktop reads the same `mcpServers` shape from `claude_desktop_config.json`. Keep secrets in environment variables, never inline.

## Versioning Strategy

- **Additive changes** (new tools, new optional parameters): non-breaking, bump minor version
- **Tool removal or rename**: breaking, requires deprecation period + major version bump
- **Required parameter addition**: breaking, consider making it optional with a default instead
- **Response format changes**: potentially breaking, document in changelog
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall