Agentset

Created By
agentset-aia year ago
Overview

what is Agentset MCP?

Agentset MCP is a server designed for managing and deploying Agentset applications using a command-line interface.

how to use Agentset MCP?

To use Agentset MCP, you need to install it via npm, yarn, or pnpm, and provide your API key and namespace ID as environment variables.

key features of Agentset MCP?

  • Easy installation using popular package managers (npm, yarn, pnpm)
  • Customizable tool descriptions and tenant IDs
  • Integration with Claude for enhanced functionality

use cases of Agentset MCP?

  1. Deploying Agentset applications in various environments.
  2. Managing multiple namespaces for different projects.
  3. Customizing tool descriptions for specific use cases.

FAQ from Agentset MCP?

  • What is the purpose of the AGENTSET_API_KEY?

The AGENTSET_API_KEY is required to authenticate your requests to the Agentset API.

  • Can I use Agentset MCP without an API key?

No, an API key is necessary to use the functionalities of Agentset MCP.

  • Where can I find the full documentation?

You can find the full documentation at Agentset Documentation.

Server Config

{
  "mcpServers": {
    "agentset": {
      "command": "npx",
      "args": [
        "-y",
        "@agentset/mcp@latest"
      ],
      "env": {
        "AGENTSET_API_KEY": "agentset_xxx",
        "AGENTSET_NAMESPACE_ID": "ns_xxx"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
agentset-ai
Star
-
Language
-
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