linkyun-ops-mcp
Provides MCP tools for querying LinkYun operations metrics, including listing metrics, querying metrics, managing agents, and home recommendations, by forwarding requests to the LinkYun Agent Ops HTTP API.
README
linkyun-ops-mcp
MCP adapter for LinkYun operations metrics.
The server exposes MCP tools for Agents and forwards every request to the
linkyun-agent Ops HTTP API. It does not connect to databases, generate SQL,
define metrics, or make authorization decisions.
Tools
ops_list_metrics: list metrics available to the configured operator token.ops_query_metric: query one backend metric with the backend query contract.ops_get_home_recommendations: get home banner/platform/hot ranking config.ops_preview_home_recommendations: validate partial home recommendation config.ops_set_home_recommendations: replace supplied home recommendation modules with audit.ops_list_agents: list/find workspace agents with operations fields.ops_get_agent: get one workspace agent by code.ops_list_agent_tags: list active tag library and discover categories.ops_update_agent: update allowed Agent operations fields with audit.
Configuration
LINKYUN_OPS_BASE_URL=http://localhost:8080
LINKYUN_OPS_TOKEN=ops_...
LINKYUN_OPS_CLIENT=linkyun-ops-mcp
LINKYUN_OPS_TIMEOUT_MS=10000
Development
npm.cmd install
npm.cmd run build
npm.cmd test
npm.cmd run lint
openspec validate ops-mcp-adapter-mvp --strict
openspec validate ops-agent-management-tools --strict
Claude Desktop Example
{
"mcpServers": {
"linkyun-ops": {
"command": "node",
"args": ["D:/Projects/linkyun/linkyun-ops/linkyun-ops-mcp/dist/index.js"],
"env": {
"LINKYUN_OPS_BASE_URL": "http://localhost:8080",
"LINKYUN_OPS_TOKEN": "ops_..."
}
}
}
}
Agents must convert relative time phrases into explicit RFC3339 timestamps
before calling ops_query_metric.
Metric Notes
ops_query_metric forwards metric codes to the backend Ops API. Adding a new
backend metric usually does not require an MCP tool schema change unless the
query contract itself changes.
Common backend metric codes:
accounts_createdregistered_usersagents_createdchat_messagesagent_assistant_messagesagent_likesmoment_likesmoment_favorites
agent_likes, moment_likes, and moment_favorites support rank in the
backend. They also accept optional agent_code for aggregate, timeseries, and
compare queries; for Moment metrics, agent_code means Moments belonging to
that Agent.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.