Gotoolkits_mcp Difyworkflow Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Gotoolkits_mcp Difyworkflow Server?

Gotoolkits_mcp Difyworkflow Server is a server application that facilitates the query and invocation of Dify workflows, allowing for the on-demand operation of multiple custom workflows.

How to use Gotoolkits_mcp Difyworkflow Server?

To use the server, clone the repository from GitHub, build the application using Go or Make, and configure the server with the necessary API keys and workflow names.

Key features of Gotoolkits_mcp Difyworkflow Server?

  • Supports multiple custom Dify workflows
  • Allows listing and executing workflows on demand
  • Easy configuration with JSON format

Use cases of Gotoolkits_mcp Difyworkflow Server?

  1. Automating tasks using predefined workflows.
  2. Integrating with other applications to execute workflows based on user input.
  3. Managing and executing workflows for data processing tasks.

FAQ from Gotoolkits_mcp Difyworkflow Server?

  • How do I install Gotoolkits_mcp Difyworkflow Server?

You can install it by cloning the repository and building it using Go or Make.

  • Can I customize the workflows?

Yes! You can define your own workflow names and API keys in the configuration.

  • What programming language is used for this project?

The project is built using the Go programming language.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago