PolyMCP

Source#

• Repository: poly-mcp/PolyMCP
• Last source update: 2026-04-04
• 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: polymcp-repo-derived-worker
name: PolyMCP Repo-Derived Worker
version: 1.0.0
source_registry_url: https://worker.md/registry/polymcp/
source_repository: https://github.com/poly-mcp/PolyMCP
repository_default_branch: main
repository_language: TypeScript
repository_license: MIT
repository_updated_at: 2026-04-04
worker_mode: tool-gateway-worker
derivation_method: github_repository_metadata_plus_raw_readme
derivation_confidence: 0.95
derived_on: 2026-04-05
tags:
  - agent-framework
  - ai-agent
  - anthropic
  - code-mode-mcp
  - llm-integration
  - mcp
---

# PolyMCP Repo-Derived Worker

## Repo-derived summary
- Registry summary: Polymcp provides a simple and efficient way to interact with MCP servers using custom agents
- Repository description: Polymcp provides a simple and efficient way to interact with MCP servers using custom agents
- Stars (snapshot): 165
- Primary language: TypeScript
- Worker mode classification: tool-gateway-worker

## Extracted from
- https://github.com/poly-mcp/PolyMCP
- https://github.com/poly-mcp/PolyMCP/blob/main/README.md

## Evidence notes (from repository text)
- README summary paragraph: > Universal MCP toolkit and agent framework for Python and TypeScript.
- > Universal MCP toolkit and agent framework for Python and TypeScript.
- PolyMCP gives teams one consistent way to expose tools, connect MCP servers, and run agents that orchestrate those tools. It ships in Python and TypeScript, plus a standalone Inspector and an MCP Apps SDK.
- - MCP clients over HTTP, stdio, or in-process transports
- - Agents that orchestrate one or more MCP servers
- - 🦞 Autonomous OpenClaw-style execution agent workflows with PolyClaw (Docker-first)

## Installation hints found in README
- `pip install polymcp`
- `pip install -e .[dev]`

## 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: polymcp-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/polymcp/

Source URL: https://github.com/poly-mcp/PolyMCP