Results for “client”

MCP client: connect servers, register tools (stdio/HTTP).

MCP client: connect servers, register tools (stdio/HTTP).

Read-only EVM client: wallets, tokens, gas across 8 chains.

Read-only EVM client: wallets, tokens, gas across 8 chains.

Add a batteries-included agent component to React/Next.js apps with runtime, streaming, human-in-the-loop approvals, and client-side tools.

GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.

Add MCP Server mode to Hermes — expose Hermes tools to external AI clients via Model Context Protocol

Send messages to WeCom (企业微信) via webhooks using MCP protocol. Works with Claude Code, Claude Desktop, and other MCP clients.

Complete MCP ecosystem — native client configuration, mcporter CLI, ACP subagent integration (Cursor, Claude Code), MCP server mode, and application-specific MCP integrations.

Integrates Dify with external systems via REST APIs, webhooks, and the MCP protocol, including client and server implementations.

`task-agent`: use when error codes, safe messages, retryability, remediation, status mapping, or client behavior needs a stable contract; skip when no error contract changes.

Test C# MCP servers at unit and integration levels using xUnit, Moq, and the MCP client SDK.

Trigger: security rules, credential leaks, auth tokens, input sanitization, threat model. Scope: Software security guidelines, threat prevention, secure data handling. Boundary: Excludes client-side web browser vulnerabilities.

Use when the user wants to build, extend, or debug the Python MCP bridge that exposes Mermate actions and stage flows to OpenClaw or other MCP clients.

Build cross-platform AI chat interfaces with Makepad using MolyKit, including async utilities, chat widgets, and OpenAI-compatible client integration.

Build, debug, and extend MCP servers and clients that connect AI systems with external tools and data sources.

Explains the domain concepts of the cuOpt REST server, including supported problem types, request flow, and key endpoints, without deployment or client code.

Agent profile for review pricing, invoices, subscriptions, entitlements, revenue logic, tax-sensitive flows, and billing UX. Use when Codex needs a specialist agent perspective for planning, implementation, review, debugging, validation, or handoff in this domain.

Build and maintain a structured personal-context portfolio for the project owner — identity, working style, goals, team, decision patterns. Includes both an interview protocol for bootstrapping and observable-signal patterns for incremental refinement. Use to bootstrap an owner profile (interview), to refine an existing profile (target one file), or to incrementally update the profile based on observed patterns from a normal session (the agent watches for signals and proposes additions when evidence accrues).

Set up a monday.com account for an OpenClaw agent and work with monday.com boards, items, and updates via the GraphQL API or MCP server. Use when: creating a monday.com workspace for a PA, connecting the PA to monday.com, querying boards and items, creating or updating items, troubleshooting monday.com API access, self-registering an agent on monday.com via HATCHA agent verification, or integrating with monday.com workflows. Covers GraphQL cookbook, column types, MCP configuration, and HATCHA self-registration. Works with any LLM model.

Interface for MCP (Model Context Protocol) servers via CLI. Use when you need to interact with external tools, APIs, or data sources through MCP servers, list available MCP servers/tools, or call MCP tools from command line.

Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.

List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.

Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.

Scaffold and implement Model Context Protocol (MCP) servers that expose external services, APIs, and data sources as typed tools and resources for LLM agents. Use when the user says "build an MCP server", "give Claude access to X", "create an MCP tool", "expose my API to an agent", or "AI agent integration".

Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.

Inspect or select a Clade execution connection while keeping agent runtime, inference provider, wire protocol, and model distinct. Use for Claude/Codex runtime selection, Anthropic/OpenAI/MiniMax/Kimi/custom gateways, model routing, or connection troubleshooting.

Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.

Connects error monitoring to MCP clients, enabling issue search, stack trace analysis, performance investigation, and AI-powered root cause analysis.

Reference for building real-time voice and multimodal AI applications with Daily and Pipecat, covering pipeline architecture, AI service integrations, transports, and client SDKs.