golf

Source#

• Repository: golf-mcp/golf
• Last source update: 2026-04-03
• Last verified: 2026-04-05

Tags#

Integration notes#

Repository is focused on tool/server interoperability; wrap in bounded worker contracts for production use.

worker.md example#

Starter worker.md contract mapped from this registry entry. Copy this file and adapt schemas, constraints, and statuses for your task.

---
id: golf-repo-derived-worker
name: golf Repo-Derived Worker
version: 1.0.0
source_registry_url: https://worker.md/registry/golf/
source_repository: https://github.com/golf-mcp/golf
repository_default_branch: main
repository_language: Python
repository_license: Apache-2.0
repository_updated_at: 2026-04-03
worker_mode: tool-gateway-worker
derivation_method: github_repository_metadata_plus_raw_readme
derivation_confidence: 0.95
derived_on: 2026-04-05
tags:
  - agent-runtime
  - ai
  - ai-agent
  - ai-agent-tools
  - ai-agents
  - ai-platform
---

# golf Repo-Derived Worker

## Repo-derived summary
- Registry summary: Production-Ready MCP Server Framework • Build, deploy & scale secure AI agent infrastructure • Includes Auth, Observability, Debugger, Telemetry & Runtime • Run real-world MCPs powering AI Agents
- Repository description: Production-Ready MCP Server Framework • Build, deploy & scale secure AI agent infrastructure • Includes Auth, Observability, Debugger, Telemetry & Runtime • Run real-world MCPs powering AI Agents 
- Stars (snapshot): 821
- Primary language: Python
- Worker mode classification: tool-gateway-worker

## Extracted from
- https://github.com/golf-mcp/golf
- https://github.com/golf-mcp/golf/blob/main/README.md
- https://docs.golf.dev

## Evidence notes (from repository text)
- README summary paragraph: Golf is a **framework** designed to streamline the creation of MCP server applications. It allows developers to define server's capabilities—*tools*, *prompts*, and *resources*—as simple Python files within a conventional directory structure. Golf then automatically discovers, parses, and compiles these components into a runnable MCP server, minimizing boilerplate and accelerating development.
- Easiest framework for building MCP servers
- This command creates a new directory (`your-project-name`) with a basic project structure, including example tools, resources, and a `golf.json` configuration file.
- This will start the MCP server, typically on `http://localhost:3000` (configurable in `golf.json`).
- ├─ tools/ # Directory for tool implementations
- Creating a new tool is as simple as adding a Python file to the `tools/` directory. The example `tools/hello.py` in the boilerplate looks like this:

## Installation hints found in README
- `pip install golf-mcp`

## worker.md contract (derived starter)
Purpose: Expose repository-supported tool/server capabilities behind a bounded worker interface.

### Input schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "request_id",
    "operation",
    "payload"
  ],
  "properties": {
    "request_id": {
      "type": "string"
    },
    "operation": {
      "type": "string"
    },
    "payload": {
      "type": "object"
    }
  }
}
```

### Output schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "request_id",
    "status",
    "result"
  ],
  "properties": {
    "request_id": {
      "type": "string"
    },
    "status": {
      "type": "string",
      "enum": [
        "ok",
        "retryable_error",
        "invalid_request",
        "invalid_output"
      ]
    },
    "result": {
      "type": "object"
    }
  }
}
```

### Constraints
- timeout_seconds: 30
- max_attempts: 2
- idempotency_key: request_id
- status_enum: [ok, retryable_error, invalid_request, invalid_output]
- notes: adapt to concrete APIs/classes documented in this repository before production use

## How this should be used
1. Treat this file as a repo-derived starter profile, not a claim of an official repository API contract.
2. Replace schemas with exact interfaces from code/docs you adopt.
3. Keep execution bounded and auditable using worker protocol constraints.

How to use#

• Save this as a worker spec file (for example: golf-my-task.worker.md).
• Replace the input/output schemas and purpose with your real bounded task.
• Enforce schema validation + timeout + retry policy in your runtime before production use.

Citation#

Reference URL: https://worker.md/registry/golf/

Source URL: https://github.com/golf-mcp/golf