"A tool to create MCP Tools in Curser" matching MCP servers:

A dynamic service that creates and manages Model Context Protocol (MCP) servers, allowing users to spawn, customize, and control multiple MCP servers as child processes.

An MCP relay that adds a use_jev tool to every connected server, letting the Jev model autonomously select and execute tool calls while the calling model supplies any required text values. It enables agents to delegate multi-step tool use across all configured MCP servers through a single unified interface.

MCP server that routes natural language requests to structured tool calls using a LoRA-tuned small language model, with built-in validation, retry, and fallback recovery.

Enables Codex to rank available tools and skills, rerank code and documentation search results, and triage saved output artifacts using Jev-based relevance scoring while leaving final decisions to Codex.

Graph-based tool retrieval for LLM agents. Builds a tool graph from OpenAPI/MCP specs and retrieves multi-step workflows via hybrid search (BM25 + graph traversal + embedding), recovering accuracy from 12% to 82% with 79% fewer tokens. Also works as an MCP Proxy to aggregate multiple servers behind 3 meta-tools.

A single MCP server that provides dynamic access to thousands of APIs through discovery and proxy, eliminating the need to install and configure multiple separate MCP servers.

Enables Codex to manage a local Claude Code companion through MCP, implementing a dual-agent workflow where Codex handles reasoning and review while Claude Code performs engineering tasks.

Enables centralized proxy and orchestration of MCP servers, providing unified tool discovery, authentication, and secure request routing. It adds a human-in-the-loop approval gate for high-risk actions and audit logging.

Enables AI coding agents to request a second opinion from a different frontier model via a single tool call, with PII scrubbed before transit, live web search, and support for Claude, ChatGPT, Cursor, and Gemini.

Enables agents to send only the handful of tool definitions relevant to each question, ranking a large catalog by keywords and optional embeddings to cut context cost and wrong-tool picks. It can also run in front of any mcpServers config as a proxy that exposes just search_tools and call_tool instead of the whole catalog.

Enables locally configured MCP servers to be called over stdio and mixed with xAI server-side tools, without relying on hosted xAI MCP.

Enables AI agents to request an independent second opinion from a different frontier model, with PII scrubbing before transit, live web search grounding, caching, and multi-provider failover.

Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.

A generic MCP proxy that filters which tools are exposed from a remote MCP server, reducing context window token usage by only loading the tools you actually need.

A configurable MCP gateway that runs multiple Streamable HTTP MCP servers and exposes all their tools through a single endpoint, enabling tool aggregation and routing for MCP clients.

Reference implementation of a Model Context Protocol server for integrating external APIs as agent tools. Includes built-in tools for weather, database queries, web search, and calculations, with authentication, rate limiting, and logging.

A framework for building hot-loadable MCP tools that feature conversational negotiation, graduated permissions, and zero-downtime updates. It enables persistent state continuity across server restarts and provides a hypothetical evaluation system for tool actions.

An MCP (Model Context Protocol) server implementation using HTTP SSE (Server-Sent Events) connections with built-in utility tools including echo, time, calculator, and weather query functionality.

An MCP proxy that embeds tool definitions and returns only the top-k semantically relevant tools per query, reducing context usage and routing calls to upstream MCP servers.

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.