Jobworkerp MCP Proxy Server (Experimental)

What is Jobworkerp MCP Proxy Server (Experimental)?

Jobworkerp MCP Proxy Server is a proxy server that mediates between remote jobworkerp-rs servers and MCP tools. It converts MCP tool list and call_tool requests into asynchronous jobs for jobworkerp-rs and returns results to the client.

How to use Jobworkerp MCP Proxy Server (Experimental)?

Build with cargo build, then run one of the four binaries: sse-server, stdio-server (all-in-one mode), sse-proxy-server, or stdio-proxy-server (proxy mode). Configure environment variables or a .env file to set the bind address, jobworkerp server URL, timeout, and log level.

Key features of Jobworkerp MCP Proxy Server (Experimental)

• Proxies MCP client requests to a jobworkerp server as async jobs
• Supports all-in-one mode with embedded jobworkerp-rs
• Supports proxy mode connecting to an existing jobworkerp server
• Enables LLMs to automatically create reusable workflows
• Runs as a single binary or a separate proxy process

Use cases of Jobworkerp MCP Proxy Server (Experimental)

• Deploying MCP tools on top of an existing jobworkerp infrastructure
• Local development and testing with a single all-in-one binary
• Scaling job execution across distributed jobworkerp workers
• Building reusable workflows that can be triggered by MCP clients

FAQ from Jobworkerp MCP Proxy Server (Experimental)

What are the two operation modes?

All-in-One mode packs the jobworkerp server into a single binary; Proxy mode connects to a separate remote jobworkerp server.

How do I configure the server?

Set environment variables like MCP_ADDR, JOBWORKERP_ADDR, REQUEST_TIMEOUT_SEC, and RUST_LOG, or use a .env file copied from the sample dot.env.

What transports are supported?

The server supports SSE (Server-Sent Events) and stdio transports, each with dedicated binaries.

Can I use Jobworkerp MCP Proxy Server with Claude Desktop?

Yes. Add the stdio-server binary to Claude Desktop’s configuration file with appropriate environment variables to integrate.

What are the main environment variables?

Key variables: MCP_ADDR (bind address), JOBWORKERP_ADDR (target jobworkerp URL), REQUEST_TIMEOUT_SEC (timeout seconds), RUST_LOG (log level), and EXCLUDE_RUNNER_AS_TOOL / EXCLUDE_WORKER_AS_TOOL to reduce context.