Modes MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Modes MCP Server?

Modes MCP Server is a server application designed for managing custom operational modes for Roo, providing programmatic control over mode configuration and management.

how to use Modes MCP Server?

To use the Modes MCP Server, clone the repository, install the dependencies, and configure the environment variables and custom modes as per the provided examples.

key features of Modes MCP Server?

  • Full CRUD operations for custom modes
  • Schema validation with Zod
  • File system watching for configuration changes
  • Error handling with standard MCP error codes
  • Atomic file operations

use cases of Modes MCP Server?

  1. Managing operational modes for software applications
  2. Customizing configurations for different user roles
  3. Automating mode transitions based on system requirements

FAQ from Modes MCP Server?

  • Can I create custom modes?

Yes! You can create, update, and delete custom modes using the provided API.

  • How do I configure the server?

Configuration is done through environment variables and JSON files as outlined in the documentation.

  • Is there support for error handling?

Yes! The server includes standard error handling for various scenarios.

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

Recommend Servers

View All
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.

8 hours ago