mcp-trigger

Created By
ai-mcpxa year ago
mcp server for trigger
Overview

what is mcp-trigger?

mcp-trigger is a server designed for managing triggers in the MCP (Minecraft) environment, allowing users to automate various tasks and events within the game.

how to use mcp-trigger?

To use mcp-trigger, set up the server by following the installation instructions on the GitHub repository, and configure the triggers according to your needs.

key features of mcp-trigger?

  • Easy setup and configuration for triggers
  • Supports various automation tasks within Minecraft
  • Open-source with an MIT license

use cases of mcp-trigger?

  1. Automating in-game events based on player actions
  2. Managing server commands triggered by specific conditions
  3. Enhancing gameplay experience through custom triggers

FAQ from mcp-trigger?

  • Is mcp-trigger free to use?

Yes! mcp-trigger is open-source and free to use under the MIT license.

  • Can I customize the triggers?

Yes! You can customize triggers based on your specific requirements by modifying the configuration files.

  • Where can I find the documentation?

Documentation is available on the GitHub repository at https://github.com/ai-mcpx/mcp-trigger.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ai-mcpx
Star
0
Language
-
License
MIT 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)

a day ago