MCP.so
ログイン

Paul Walker's Bespoke MCP Tools

@pauldw

基本情報

カテゴリ

その他

トランスポート

stdio

作者

pauldw

Paul Walker's Bespoke MCP Tools について

MCP Server with an artisinal selection of bespoke agent tools.

Paul Walker's Bespoke MCP Tools の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Paul Walker's Bespoke MCP Tools のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Paul Walker's Bespoke MCP Tools?

A shifting collection of one‑off MCP tools built by Paul Walker. Currently includes tools to manage a task queue (push‑tasks, pop‑task) and to launch, monitor, and kill background shell processes (launch‑background‑process, get‑process‑output, kill‑process, wait).

How to use Paul Walker's Bespoke MCP Tools?

Install via Goose by using the provided goose:// link or by adding a Standard IO extension with the command npx -y github:pauldw/pwalker-mcp. For local development, run npm --prefix /path/to/local/copy run start.

Key features of Paul Walker's Bespoke MCP Tools

  • Queue management: add tasks (push‑tasks) and retrieve the next task (pop‑task)
  • Launch shell commands in the background (launch‑background‑process)
  • Retrieve output of previously launched processes (get‑process‑output)
  • Kill running background processes (kill‑process)
  • Pause execution for a specified number of seconds (wait)

Use cases of Paul Walker's Bespoke MCP Tools

  • Automate task queues by pushing items and popping them sequentially
  • Run long‑running shell scripts without blocking the main MCP session
  • Monitor and control background processes from within an MCP client
  • Add artificial delays between steps in a workflow with the wait tool

よくある質問

1

What does this server do?

It provides a set of MCP tools for task queue operations and background process management, intended as a personal experimental collection.

2

Which tools are currently included?

`push‑tasks`, `pop‑task`, `launch‑background‑process`, `get‑process‑output`, `kill‑process`, and `wait`.

3

How do I install it?

Use the Goose extension link or manually add a Standard IO extension with the command `npx -y github:pauldw/pwalker-mcp`.

4

What dependencies are required?

`node` and `npm` are needed to run the server via `npx` or local development.

5

Where does the task queue data live?

The README does not specify persistence details; the queue likely lives in memory for the duration of the MCP session.

コメント

「その他」の他のコンテンツ