Workflow MCP Server

Created By
tuanknguyena year ago
Overview

what is Workflow MCP Server?

Workflow MCP Server is a Python-based server designed to guide agents through structured workflows, ensuring they follow predefined steps while allowing flexibility in execution.

how to use Workflow MCP Server?

To use the Workflow MCP Server, set up your environment using the UV package management tool, create a virtual environment, install the package, and run the server using the provided commands.

key features of Workflow MCP Server?

  • Structured workflow guidance for agents
  • Flexibility in executing predefined steps
  • Easy package management with UV
  • YAML-based workflow definition

use cases of Workflow MCP Server?

  1. Automating business processes with defined workflows.
  2. Guiding customer support agents through troubleshooting steps.
  3. Managing complex project workflows in software development.

FAQ from Workflow MCP Server?

  • What is UV and why should I use it?

UV is a package management tool that provides faster and more reliable operations compared to traditional tools.

  • Can I run multiple workflows simultaneously?

Yes, you can start multiple workflow sessions as needed.

  • Is there a way to test my workflows?

Yes, you can run tests using the command uv run pytest.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tuanknguyen
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago
Voyei

7 hours ago