Skip to content

MCP servers for workflow governance

19 MCP servers for workflow governance. Each one shows how to install it in Claude, Cursor and VS Code, whether it runs locally or remotely, and the tools it provides.
  1. Reach your Dash AI teammate and workspace tools from any MCP client

    Not checked yet
    • Remote
    • Freemium
    • Productivity
  2. MCP server for building AI agent services with checked handoffs and set limits

    Not checked yet
    • Remote
    • Freemium
    • Workflow governance
  3. One shared project plan that people and their AIs read and write over MCP

    Not checked yet
    • Remote
    • Freemium
    • Productivity
  4. A shared check so agents avoid duplicate work: look, claim, check, mark

    Not checked yet
    • 4 tools
    • Remote
    • Freemium
    • Workflow governance
  5. SOP templates and process documentation tools for small operations teams

    Not checked yet
    • Remote
    • Freemium
    • Productivity
  6. Policy and procedure register with owners, versions and signed attestations

    Not checked yet
    • Remote
    • Free trial
    • Workflow governance
  7. Governed gateway giving AI clients access to enterprise systems of record

    Not checked yet
    • Remote
    • Contact sales
    • Mcp data access
  8. Overview, FAQ search and install guide for the Bureau self-hosted agent office

    Not checked yet
    • Remote
    • Open source
    • Knowledge and memory
  9. Shared goals, leased tasks, handoffs and review for autonomous AI agents

    Not checked yet
    • Remote
    • Free
    • Knowledge and memory
  10. Publish client-side apps and share them by link, with company governance

    Not checked yet
    • Remote
    • Freemium
    • Developer tools
  11. Build and test short-form marketing automations from your agent, no posting

    Not checked yet
    • 16 tools
    • Remote
    • Paid
    • Marketing and SEO
  12. Let an agent log what it finished into a team's standup feed

    Not checked yet
    • Remote
    • Freemium
    • Productivity
  13. Check client requests against a confirmed scope: included, extra or unclear

    Not checked yet
    • Remote
    • Freemium
    • Workflow governance
  14. Operate Faldaro forms, submissions and workflows from an MCP client

    Not checked yet
    • Remote
    • Form backend
  15. Approval gateway that holds AI-agent API writes for owner sign-off

    Not checked yet
    • Remote
    • Freemium
    • Agent approvals
  16. Approve, file and track documents in SORNFlow from your AI assistant

    Not checked yet
    • Remote
    • Freemium
    • Files and documents
  17. Shared task queue where agencies delegate client work to people and AI agents with signed

    Not checked yet
    • Remote
    • Freemium
    • Workflow governance
  18. MCP server connecting AI assistants to Foqal's ticketing and workflow platform for support

    Not checked yet
    • Remote
    • Communication

See every kind of AI for workflow governance: tools, agents, MCP servers and skills.Ranked: the best AI for workflow governance.

Questions about MCP servers for workflow governance

What are the best MCP servers for workflow governance?

The most popular MCP servers for workflow governance on AI-Powered right now are Dash, UltraTeams, Rowbrief, AstraNL Crossing and RunbookDesk. Rankings combine upvotes, recent activity and, for open-source projects, GitHub stars.

Are there free MCP servers for workflow governance?

Yes. Of the 19 MCP servers for workflow governance listed, 2 are free or open source and 11 have a free plan. Use the Pricing filter to see only those.

How many MCP servers for workflow governance are there?

AI-Powered lists 19 MCP servers for workflow governance. New listings are added daily from the official MCP Registry, GitHub and maker submissions.

How do I install one of these MCP servers for workflow governance?

Open the server's page and copy the snippet for your client. Claude Code uses a single "claude mcp add" command; Claude Desktop, Cursor and VS Code use a JSON entry in their MCP config file. Remote servers only need their URL.