"Creating a Memory Database for LLM Chat Conversations" matching MCP servers:

Wraps Tool and ToolPackage instances from the llm-chat ecosystem behind the Model Context Protocol, enabling stdio and Streamable HTTP transports for MCP servers.

Enables agents to inspect configured LLM models and send chat requests to them, with support for parameter overrides, file-based prompts, and output to files.

Blind multi-model councils with anonymous LLM seats and direct 1:1 chat as a local MCP server. Enables asking one question to get independent answers from multiple model CLIs, then blind scoring and reveal.

Provides a local chat room for coordinating work across Git worktrees, coding agents (Claude, Codex), and humans, with tools to start, wake, stop, message, and search agent sessions.

Enables remote control of the Cursor AI agent via chat platforms like GitHub Issues or Telegram, allowing users to start sessions and receive summaries and prompts in a chat thread.

A local MCP gateway that unifies multiple LLM providers, API keys, routing, and multi-model discussions into a single tool surface.

Enables a primary agent to offload bounded, high-volume analysis of explicitly selected workspace files to an auxiliary LLM through a single read-only tool, returning text, Markdown, JSON, or unified-diff output with token usage while retaining all planning, verification, and edits.

Enables remote chat between Feishu (Lark) and AI agents like Cursor/Claude via MCP, allowing users to send messages from Feishu groups and receive streaming replies.

MCP server that provides a live coordination layer for AI agents, including attributable handoffs, a shared event ledger, atomic work-claiming, and advisory file leases to prevent collisions.

MCP server for the LLM Wiki Chrome extension that exposes bounded browser automation tools (shared tabs, accessibility snapshots, screenshots, clicks, typing, etc.) with explicit user consent and strict typing, enabling local agents to interact with specific web pages via a native messaging relay.

An MCP server that routes LLM requests across multiple providers and orchestrates other MCP servers, with a focus on local privacy for embeddings and memory.

A small MCP server that lets Claude (or any MCP client) ask other models what they think.

Exposes local stdio MCP servers to chat AIs through temporary public URLs, providing both a Streamable HTTP gateway and a REST+OpenAPI bridge for integration with ChatGPT and other clients.

Enables AI coding agents to collaborate on the same project by sharing session briefs and reading each other's native transcripts, memories, and instructions in place, with zero-copy, across different agent tools.

Enables AI agents to send messages to human users via chat platforms (currently Discord) and optionally wait for human responses, facilitating human-in-the-loop interactions.

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 AI agents to control a Playwright-driven browser through natural-language instructions, including page interaction and live browser task execution.

Enables cost-aware LLM routing over MCP with verification-based cascading, offering tools for routing queries, resuming escalated approvals, estimating costs, comparing policies, and explaining routing decisions, plus read-only resources and a policy-selection prompt.

A local-first LLM routing MCP server that keeps sensitive data on your own models, with fail-closed privacy and manager-worker delegation, exposing route and complete tools to any MCP client.

Enables delegating mechanical or high-volume subtasks to a local LLM through an MCP tool, letting the assistant query the local model without using its own output tokens for content.