腾讯云HAI MCP服务器

Created By
avacxa year ago
腾讯云HAI Model Context Protocol (MCP)服务器
Overview

what is HAI MCP Server?

HAI MCP Server is a Model Context Protocol (MCP) server that connects to Tencent Cloud HAI (Hunyuan AI) services, allowing applications like Claude Desktop/Cline to directly call Tencent Cloud HAI APIs.

how to use HAI MCP Server?

To use HAI MCP Server, you can clone the repository from GitHub, install dependencies, and run the server using command line or Docker. You can also configure it within Claude Desktop/Cline for seamless integration.

key features of HAI MCP Server?

  • List Tencent Cloud HAI instances
  • Retrieve detailed information about specific HAI instances
  • Check the status of HAI instances
  • Filter HAI instances based on their status
  • Provide HAI instance information as resources
  • Analyze HAI instance configurations and provide recommendations

use cases of HAI MCP Server?

  1. Managing and monitoring Tencent Cloud HAI instances.
  2. Integrating HAI services into applications like Claude Desktop/Cline.
  3. Automating the retrieval of HAI instance information for reporting or analysis.

FAQ from HAI MCP Server?

  • Can HAI MCP Server connect to all Tencent Cloud HAI services?

Yes! HAI MCP Server is designed to connect to various Tencent Cloud HAI services.

  • Is HAI MCP Server free to use?

Yes! HAI MCP Server is open-source and free to use.

  • How do I install HAI MCP Server?

You can install it by cloning the GitHub repository, using pip, or via Docker.

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