Projeto: Servidor MCP de Automação Residencial

Created By
douglasinforja year ago
Projeto de aprendizado sobre assunto Servidor MCP
Overview

what is Servidor MCP de Automação Residencial?

Servidor MCP de Automação Residencial is a project focused on learning about MCP servers for home automation.

how to use Servidor MCP de Automação Residencial?

To use the project, you can execute commands via the terminal to control various home automation features.

key features of Servidor MCP de Automação Residencial?

  • Control lights (turn on/off)
  • Adjust temperature settings
  • Lock/unlock doors
  • Check overall status of the home automation system

use cases of Servidor MCP de Automação Residencial?

  1. Automating lighting in a home environment.
  2. Managing temperature settings for energy efficiency.
  3. Enhancing home security by controlling door locks.

FAQ from Servidor MCP de Automação Residencial?

  • What commands can I use?

You can use commands to control lights, temperature, and door locks.

  • Is there a graphical interface?

No, the current implementation is command-line based.

  • Can I integrate it with other home automation systems?

Yes, it can be integrated with other systems that support command-line interfaces.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
douglasinforj
Star
0
Language
-
License
-
Tags

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours 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.

a day ago