"Information about a cursor" matching MCP servers:

Enables coding agents to add a bounded semantic-judgment layer for routing, ranking, extraction, verification, and escalation, returning typed signals and review recommendations.

Enables coding agents to query the dependency graph of a GitHub backlog, retrieve ordered ready work and prerequisite chains, atomically claim issues, and report blockers—so agents work in the correct order and safely in parallel.

Enables agents to get fast, calibrated probabilistic answers from Jev (Typesafe AI) to yes/no, scale, or choice questions about provided material, without using a generative model.

Provides versioned, structured memory for AI agents, allowing them to store facts, detect conflicts, and track knowledge history via a hosted SaaS platform. It enables efficient hierarchical information retrieval and semantic search while keeping token usage constant as memory scales.

Procedural memory for coding agents: not facts about the user, but how a task was solved — trigger, steps, outcome, lessons. Hooks recall it automatically; skills strengthen only on outside evidence and unused ones decay. Each memory carries its provenance and only the owner approves one as a rule. Local SQLite + FTS5, no API key, no cloud. One database for Claude Code, Codex and Cursor.

Discover and connect your agents with other agents via A2A protocol. Share resources for free or fee.

Run DeepSeek as a real sub-agent inside Claude Code / Codex CLI — not just a single LLM call. DeepSeek gets its own 7-tool agent loop (Read/Write/Edit/Bash/Glob/Grep/NotebookEdit) inside a sandboxed workspace.

An improved implementation of persistent memory using a local knowledge graph with a customizable --memory-path. This lets Claude remember information about the user across chats.

Delegate a Cursor task to a real, unattended background OpenCode agent — cheaper model, isolated history — through five small MCP tools.

Monitors your Cursor usage and provides a conserve flag to the agent, helping you manage request quota by batching questions, preferring defaults, and cutting unnecessary confirmations.

Enables AI agents to participate in meetings by pulling pending requests, reading context, and submitting answers through a Supabase-based MCP server.

An MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.

Mandatory human approval gate for autonomous AI agents. Before any critical, irreversible, or financially significant action executes — file deletion, production deployment, financial transaction — the agent calls oracle_validate. A human receives a real-time Telegram notification with full context and taps Approve or Reject. The agent waits for the decision before proceeding.

Enables AI assistants and other MCP clients to launch and steer Cursor Cloud Agents on repositories or as repo-less research tasks, including model selection, mid-run follow-ups, cancellation, result retrieval, and run listing. Also exposes authentication checks and per-agent or per-run token usage and cost reporting.

An MCP server that enables local AI models to receive guidance from remote 'senior' AI providers like OpenAI, Anthropic, and Gemini to solve programming problems. It features intelligent multi-turn dialogue management, context synchronization, and automated session history tracking.

Enables a host AI agent to trigger a multi-agent debate, running N-rounds where agents critique each other's answers, then synthesizes a consensus recommendation with ranked options.

Enables an orchestrator like Claude Code to hand coding work off to Cursor SDK agents, run as detached background jobs that survive the session and can be listed, inspected, steered, resumed, or stopped. Agents are asynchronous and reusable across follow-up turns, letting expensive frontier models delegate cheaply without blocking or paying to read the results.

Allows AI assistants to access and analyze your Cursor conversation history, enabling personalized coding assistance based on your actual development patterns.

Provides a hybrid memory architecture with a thin SQLite index and Markdown cold storage, enabling AI agents to write, query, link, and rebuild long-term memories via MCP tools, model-agnostic and zero third-party dependencies.

Lets separate coding-agent sessions coordinate through a shared, role-addressed mailbox instead of a human relaying every message, over a single local SQLite file or a hosted server with many isolated channels. Messages can be sent as tracked obligations that stay open until one side resolves and the other confirms, alongside threads, full-text search, work statuses, and an append-only versioned pin system where protected changes require recorded agreement from every declared role.