Results for “server”

Use whenever the user wants to find, rank, or shortlist directories and registries where they can submit or list an MCP server (Model Context Protocol server) — to get backlinks, referral traffic, and discovery by agent builders. Triggers on "where do I list my MCP server", "best MCP directories", "MCP registries to submit to", "get my MCP server discovered", or "pull submission details for these MCP-directory domains", even when described indirectly (we built an MCP server, where do we publish it). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-ai-directories for general AI-tool / AI-agent / agent-skill listings, and to find-product-directories for general SaaS/software launches. Skip building an MCP server or asking how MCP works (DIY), finding a firm to build one (use find-ai-consultancy / find-software-developer), and MCP link-building *services*.

The English summary is being prepared. Showing the original description.

Audit server-side paid-media measurement including server-side tag management, platform conversion APIs, event taxonomy, browser/server deduplication, consent, hashing, data quality, observability, and privacy. Use for server-side tracking, sGTM, server-side tagging, Meta CAPI, TikTok Events API, event_id, deduplication, pixel debugging, first-party measurement, or conversion data loss.

The English summary is being prepared. Showing the original description.

AWS serverless and event-driven architecture expert based on Well-Architected Framework. Use when building serverless APIs, Lambda functions, REST APIs, microservices, or async workflows. Covers Lambda with TypeScript/Python, API Gateway (REST/HTTP), DynamoDB, Step Functions, EventBridge, SQS, SNS, and serverless patterns. Essential when user mentions serverless, Lambda, API Gateway, event-driven, async processing, queues, pub/sub, or wants to build scalable serverless applications with AWS best practices.

The English summary is being prepared. Showing the original description.

吉里吉里Z (krkrz) の -replweb HTTP+SSE サーバ (WebServer クラス) にブラウザ UI を載せて、本体アプリの操作/編集/観測パネルをブラウザ側に組み込む方法論。ゲーム本体は 3D 表示やゲーム内 UI に専念させ、編集ツール・インスペクター・ダッシュボード・REPL コンソールをブラウザ (別ウィンドウ/別PC) から使う構成を作るときに読む。プラグインや TJS がサーバへエンドポイントを追加公開する手順 (WebServer.register / serveStatic / broadcast)、ハンドラ呼び出し規約 (req %[method,path,query,body,bytes] → 文字列/octet/整数/辞書)、状態同期パターン (fetch POST + SSE /sub push + throttle + 差分/tick 配信)、既存 REPL コンソール (/events + /cmd) の UI 埋め込み、ブラウザのアプリモード起動 (Chromium --app / -webui)、json.dll 連携、TJS2 由来のハマりどころ (ローカル関数クロージャ不在→クラス化 / ブロックコメントのネスト誤爆 / startup 例外の致命性 / ハンドラは必ずメインスレッド実行) を網羅。エンジン側 WebServer クラスそのものの仕様は krkrz core doc/REPL.md、REPL/Agent 駆動は skill krkrz-repl、Elements ネイティブ UI は skill elements、TJS2 言語は skill tjs2、本体 API は skill krkrz を参照。

The English summary is being prepared. Showing the original description.

Audit server-side paid-media measurement including server-side tag management, platform conversion APIs, event taxonomy, browser/server deduplication, consent, hashing, data quality, observability, and privacy. Use for server-side tracking, sGTM, server-side tagging, CAPI, Events API, event_id, pixel debugging, first-party measurement, or conversion data loss.

The English summary is being prepared. Showing the original description.

Build, deploy, and secure Model Context Protocol (MCP) servers on Netlify. Use whenever the task involves creating an MCP server, exposing an app or API to AI agents as MCP tools, letting Claude / Cursor / Claude Code call a custom remote server, or adding MCP tools to an existing Netlify site. Covers the MCP SDK + Streamable HTTP transport on a Netlify Function, authentication (single shared secret vs per-user API keys with Netlify Identity), read/write safety, file uploads, and connecting clients. Use even when the user just says "MCP", "tool server for an agent", or "let an AI use my API".

The English summary is being prepared. Showing the original description.

Implement React Server Actions in Next.js 14+ for secure, progressively enhanced form handling and server mutations without API routes. Use when handling form submissions, performing server-side mutations, implementing progressive enhancement, creating actions that work without JavaScript, validating data on the server, revalidating cached data after mutations, handling file uploads server-side, implementing optimistic UI updates, or building forms that gracefully degrade without client-side JavaScript.

The English summary is being prepared. Showing the original description.

Agent fallback for CEngineServer_UnloadSpawnGroup (auto-generated, category: vfunc). Locate CEngineServer::UnloadSpawnGroup in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CEngineServer_UnloadSpawnGroup, CEngineServer::UnloadSpawnGroup

The English summary is being prepared. Showing the original description.

Agent fallback for CDedicatedServerWorkshopManager_SwitchToWorkshopMapGroup (auto-generated, category: func). Locate CDedicatedServerWorkshopManager::SwitchToWorkshopMapGroup in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CDedicatedServerWorkshopManager_SwitchToWorkshopMapGroup, CDedicatedServerWorkshopManager::SwitchToWorkshopMapGroup

The English summary is being prepared. Showing the original description.

Agent fallback for CDedicatedServerWorkshopManager_SwitchToWorkshopMapGroup-decompiles (auto-generated, category: func). Locate CDedicatedServerWorkshopManager::SwitchToWorkshopMapGroup in the CS2 server module via IDA Pro MCP and emit a fresh, minimal-unique artifact. The deterministic preprocessor could not resolve this symbol on the current gamever - your job is the re-sign. Trigger: CDedicatedServerWorkshopManager_SwitchToWorkshopMapGroup-decompiles, CDedicatedServerWorkshopManager::SwitchToWorkshopMapGroup

The English summary is being prepared. Showing the original description.

Agent-to-Agent (A2A) server configuration patterns for HTTP, STDIO, SSE, and WebSocket transports. Use when building A2A servers, configuring MCP transports, setting up server endpoints, or when user mentions A2A configuration, server transport, MCP server setup, or agent communication protocols.

The English summary is being prepared. Showing the original description.

Audit MCP (Model Context Protocol) server configurations for security issues. Use this skill when: - Reviewing .mcp.json files for security risks - Checking MCP server args for hardcoded secrets or shell injection patterns - Validating that MCP servers use pinned versions (not @latest) - Detecting unpinned dependencies in MCP server configurations - Auditing which MCP servers a project registers and whether they're on an approved list - Checking for environment variable usage vs. hardcoded credentials in MCP configs - Any request like "is my MCP config secure?", "audit my MCP servers", or "check .mcp.json" keywords: [mcp, security, audit, secrets, shell-injection, supply-chain, governance]

The English summary is being prepared. Showing the original description.

Coordinate updates to an operator-configured Team server through its designated Night Watch owner. Use the existing deployment controller’s validation, recovery, and acceptance records to follow the requested update through completion.

• Updating a Team server to official main
• Following up on failed or deferred updates
• Coordinating database migration and recovery

Research existing solutions before implementing a feature. Search project code, package registries, agent tools, and GitHub, then compare functionality, maintenance, licensing, and dependencies to decide whether to adopt, extend, combine, or build.

• Researching existing solutions before adding a feature
• Comparing packages before adding a dependency
• Finding tools for an external integration

Build and maintain MCP servers that let AI assistants use tools, read data, and access reusable prompts. Covers Node/TypeScript implementation, input validation, transport choices for local or remote clients, and registration or connection troubleshooting.

• Building an MCP server for AI assistants
• Adding tools, resources, and reusable prompts
• Choosing local or remote connection methods

Build MCP servers, connectors that let AI models use external services through tools. This skill guides API research, tool design, implementation in TypeScript or Python, testing, and evaluation with realistic questions that require multiple tool calls.

• Connecting an external API to an AI agent
• Building an MCP server in TypeScript or Python
• Improving tool descriptions, inputs, and error messages

Connect external services to Claude Code plugins through MCP, a protocol that exposes service functions as tools. Get guidance on server configuration, connection methods, authentication, tool permissions, and testing connections and tool calls.

• Adding a local MCP server to a plugin
• Configuring authentication for a hosted service
• Using multiple services in commands and agents

A deprecated guide to building MCP servers with mcp-use, covering callable actions, data resources, reusable prompts, and interactive widgets. It includes design references and code examples, and directs users to the replacement skill, mcp-app-builder.

• Review the structure of an existing mcp-use server
• Consult examples of tools, resources, and prompts
• Explore interactive widget design

Build MCP servers, which let Claude call external tools and read data through a shared protocol. Follow Python or TypeScript examples to implement tools, connect services, configure Claude, and test server behavior.

• Adding custom tools to Claude
• Connecting an external API
• Reading database records or settings

Check and control OmniRoute’s MCP server, which connects agents to tools. Inspect tool permission scopes, enable or restart the server, and invoke tools with JSON arguments from the command line.

• Check the MCP server’s operating status
• Enable, disable, or restart the server
• Inspect permission scopes for a tool

Build MCP servers, which give AI agents tools for external services, using Python or TypeScript. The skill guides tool design, input validation, error handling, code review, and evaluations based on realistic tasks.

• Build an MCP server for an external API
• Design tools around complete agent workflows
• Review input validation and error handling

Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.

• Verify installation and config.toml changes in isolation
• Confirm plugin hooks run during a real Codex turn
• Check terminal interface startup

Move useful memory notes and MCP server settings from Claude Code or Codex into Muse Code. MCP servers connect agents to external tools; the skill checks compatibility and reports settings that need attention.

• Bring saved preferences into Muse Code
• Import useful project memory notes
• Move MCP server settings to Muse Code

Review external integration points for breaking changes that could disrupt existing use. Examine app-server APIs, command-line parameters, configuration loading, and session resumption from saved records, continuing beyond the first issue to cover possible failure paths.

• Check app-server API compatibility
• Review changes to command-line parameters
• Check compatibility of configuration loading