nova-act-mcp-server

Created By
madtanka year ago
An MCP server providing tools to control web browsers using the Amazon Nova Act SDK. Enables multi-step browser automation workflows via MCP agents.
Overview

what is nova-act-mcp?

nova-act-mcp is an MCP server that provides tools for controlling web browsers using the Amazon Nova Act SDK, enabling users to create multi-step browser automation workflows through MCP agents.

how to use nova-act-mcp?

To use nova-act-mcp, set up the MCP server and utilize the provided tools to define and execute browser automation tasks via the Amazon Nova Act SDK.

key features of nova-act-mcp?

  • Control web browsers programmatically using the Amazon Nova Act SDK.
  • Create complex multi-step automation workflows.
  • Utilize MCP agents for efficient task execution.

use cases of nova-act-mcp?

  1. Automating repetitive web tasks such as form submissions.
  2. Scraping data from websites in a structured manner.
  3. Testing web applications through automated browser interactions.

FAQ from nova-act-mcp?

  • What is an MCP server?

An MCP server is a management control protocol server that allows for the automation of tasks across different systems, in this case, web browsers.

  • Is nova-act-mcp free to use?

Yes! nova-act-mcp is open-source and available under the MIT license.

  • Can I customize the automation workflows?

Yes! Users can define their own workflows using the tools provided by the nova-act-mcp.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
madtank
Star
12
Language
Python
License
MIT license
Tags

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