Jobworkerp MCP Proxy Server (Experimental)

Created By
jobworkerp-rsa year ago
mcp proxy server for jobworkerp-rs
Overview

What is Jobworkerp MCP Proxy?

Jobworkerp MCP Proxy is an experimental proxy server that facilitates communication between remote jobworkerp-rs servers and Model Control Protocol (MCP) tools. It acts as an intermediary, converting requests from MCP clients into asynchronous jobs for jobworkerp-rs and returning the results back to the clients.

How to use Jobworkerp MCP Proxy?

To use the Jobworkerp MCP Proxy, you can build and run the server in either All-in-One mode or Proxy mode. In All-in-One mode, it operates as a single binary that includes both the proxy server and jobworkerp server functionalities. In Proxy mode, it connects to an existing jobworkerp server.

Key features of Jobworkerp MCP Proxy?

  • Proxy MCP client requests to jobworkerp, converting them into asynchronous jobs.
  • Tool creation capabilities, including reusable workflows and custom workers.
  • Automatic tool creation using LLMs.
  • Two operation modes: All-in-One and Proxy mode for flexibility in deployment.

Use cases of Jobworkerp MCP Proxy?

  1. Integrating MCP tools with jobworkerp for asynchronous job processing.
  2. Creating reusable workflows for common tasks in job processing.
  3. Facilitating local development and testing of jobworkerp functionalities.

FAQ from Jobworkerp MCP Proxy?

  • What is the purpose of the Jobworkerp MCP Proxy?

It serves as a bridge between MCP clients and jobworkerp servers, enabling efficient job processing.

  • How do I configure the server?

You can set environment variables or use a configuration file to define server settings.

  • Is it suitable for production use?

Yes, it can be used in production environments, especially in Proxy mode for scalability.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jobworkerp-rs
Star
0
Language
Rust
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago