Utopia

Created By
Gokhan Altinorena year ago
Utopia is a simulation MCP Server designed to test and experiment with common household items, both those available today and those likely to exist in the near future, using AI Agents. This project provides a set of simulated smart home and lifestyle devices, allowing you to interact with them through AI agents.
Overview

what is Utopia?

Utopia is a simulation MCP Server designed to test and experiment with common household items, both those available today and those likely to exist in the near future, using AI Agents. This project provides a set of simulated smart home and lifestyle devices, allowing you to interact with them through AI agents.

how to use Utopia?

To use Utopia, run the server using the command dotnet run --project <path_to_project_folder>/Utopia.csproj and interact with the simulated devices through the provided tools.

key features of Utopia?

  • Simulated smart home devices for various household functions.
  • AI agents to interact with and manage household items.
  • Tools for monitoring and controlling home environments, such as humidity, air quality, and lighting.

use cases of Utopia?

  1. Testing the functionality of smart home devices before purchasing.
  2. Experimenting with different home automation scenarios.
  3. Simulating grocery shopping and managing household inventory.

FAQ from Utopia?

  • Can Utopia simulate all types of household devices?

Yes! Utopia includes a variety of simulated devices such as smart thermostats, robot vacuums, and more.

  • Is Utopia free to use?

Yes! Utopia is open-source and available for anyone to use.

  • How can I contribute to Utopia?

You can contribute by visiting the GitHub repository and submitting pull requests or issues.

Server Config

{
  "mcpServers": {
    "Utopia": {
      "command": "dotnet",
      "args": [
        "run",
        "--project",
        "<path_to_project_folder>/Utopia.csproj"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Gokhan Altinoren
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