"MCP tools for monitoring application memory and CPU usage" matching MCP servers:

An MCP server that exposes Claude Code's real-time rate limit usage so that an orchestrator can check remaining capacity before launching subtasks.

Gives the model visibility into the same 5-hour session, weekly, and per-model usage percentages shown in Claude Code, along with reset times. It also lets a project cap how much of the weekly limit may be spent via start/check/end budget tools that report OK, LOW, or OVER_BUDGET.

Provides Dify apps with a secure, app-scoped MCP tool catalog and action gateway for authorized FlowFlox operations, enabling intent-driven planning and fixed operational processes without exposing global credentials.

An MCP server that exposes 43 domain tools behind 4 meta-tools, applying guardrails such as budgets, rate limits, schema validation, human-in-the-loop confirmation for mutations, PII redaction, and an append-only audit log while reducing context window usage.

Enables building and evaluating LangGraph agents over a protocol-level MCP server to measure failure rates across four agent topologies.

A production-grade MCP server that provides a centralized microservice toolkit for LLM agents, enabling web search and extensible tool integration.

A meta-MCP server that orchestrates tools from multiple MCP servers, enabling complex Python workflows with loops and conditionals.

Exposes OpenClaw tools (web search, page fetching, browser automation, PDF analysis, messaging, inter-agent communication, Canvas) as MCP tools for ACP agents.

An advanced contextual memory server for agent orchestration providing chronological history, semantic vector search via Redis Stack, and temporary scratchpad storage. It also enables context compression through history rollups and facilitates inter-agent communication using a Redis-based Pub/Sub system.

Enables ZCode to control a real Chrome browser, including tabs, navigation, page content, clicks, form filling, keyboard input, scrolling, screenshots, and JavaScript evaluation through a local MCP bridge.

A deterministic MCP tool-list relay that lets operators filter tools by include/exclude rules and exposes a filtered stdio MCP server to local clients.

Persistence, headed Chromium browser control for MCP clients like OpenCode and Claude Code, enabling navigation, inspection, clicking, filling, and human-gated actions on JavaScript-heavy or login-walled pages.

lark-tools-mcp connects Lark and cursor. It provides cursor with the ability to read documents, send messages, process tasks, and perform data analysis.

Model Context Protocol (MCP) memory server built with Azure Functions and TypeScript, providing persistent knowledge graph storage for your preferred MCP client. Inspired by and forked from @modelcontextprotocol/server-memory

A passive MCP server that exposes a toolbox of executable tools (shell, network, HTTP, AI search, SSH, S3 file operations) to autonomous agents via Streamable HTTP, with strong security features including Docker sandboxing and WAF.

Enables MCP-compatible agents to discover and call x402 paid services from a directory of over 2,000 APIs.

Enables OpenAI-compatible clients to access external tools, APIs, repositories, and data sources through MCP with allowlisting, approval, and argument validation, deployable as a FastAPI service or Python library.

A shared memory and coordination server for multiple AI coding agents, built on the Model Context Protocol (MCP).

Provides MCP tools for persistent, cross-session memory via Cloudflare Agent Memory, enabling agents to store, recall, ingest, summarize, and manage memory namespaces.

Persistent MCP server runtime for progressively discovering and loading MCP, REST, and local CLI adapters, with host-side credentials and explicit confirmation for mutations.