Hyros MCP Server

Created By
zalogarciaa year ago
Hyros MCP Server - Model Context Protocol server providing 24 Hyros API tools for AI agents and automation platforms
Overview

What is Hyros MCP Server?

Hyros MCP Server is a Model Context Protocol server that provides seamless access to 24 Hyros API tools designed for AI agents and automation platforms, enabling efficient data management and workflow automation.

How to use Hyros MCP Server?

To use the Hyros MCP Server, you can integrate it with platforms like n8n or Claude Desktop by adding specific configurations or install it directly using npm commands.

Key features of Hyros MCP Server?

  • Access to 24 comprehensive Hyros API tools for various functionalities including lead management, sales tracking, and call management.
  • Easy integration with automation platforms like n8n and Claude Desktop.
  • Supports advanced filtering and data retrieval options for effective data management.

Use cases of Hyros MCP Server?

  1. Automating marketing workflows and lead nurturing sequences.
  2. Enhancing AI conversations with real-time access to Hyros data.
  3. Building custom AI agents for customer service and sales optimization.

FAQ from Hyros MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol (MCP) is a framework that allows seamless communication between AI agents and data sources.

  • How do I get my Hyros API key?

You can obtain your API key from your Hyros dashboard.

  • Is there support available for using the Hyros MCP Server?

Yes! You can open an issue in the repository for package issues or contact Hyros support for API-related questions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zalogarcia
Star
0
Language
JavaScript
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)

2 days ago