"Comparison of Python-based tools for converting TeX to Lean" matching MCP servers:

TEX is an MCP server that enables Claude Code to perform browser tasks using plain language, driving a real browser to interact with web applications that lack APIs.

Enables low-cost agent models to control Windows applications through a compact, state-safe proxy over Open Computer Use, reducing model-visible context by up to 99.8% with support for record/replay and reusable UI component memory.

MCP server providing virtual memory for AI context with durable SQLite storage, retrieval, and bounded prompt assembly to manage context windows.

A meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.

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.

Paybond Kit for Python is the PyPI package for tenant-bound Paybond integrations and delegated agent spend controls. It opens hosted Gateway sessions, verifies capability tokens, authorizes tool-call spend, signs intent and evidence payloads, uses Stripe Connect, Stripe ACH Direct Debit, or x402 / USDC-on-Base settlement rails, reads tenant-scoped Signal, fraud, ledger, protocol, and A2A data, and

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

A multi-agent orchestration system that enables multiple Claude instances to collaborate through a centralized hub with a shared workspace and real-time communication. It features integrated task management, role assignment, and persistent memory to facilitate complex, synchronized agent workflows.

Enables AI agents to drive real Google Chrome with stealth and captcha handling, using Patchright to avoid bot detection.

A Machine Comprehension Protocol server that enables AI assistants to interact with Kestra workflows through natural language, supporting operations like flow management, executions, backfills, and other Kestra features.

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.

Converts any REST API into MCP-compatible tools instantly by providing an OpenAPI/Swagger spec, enabling seamless integration with AI agents.

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

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 clients to interact with A2A agents through four ordinary tools, translating agent discovery, messaging, task reading, and cancellation between the A2A and MCP protocols, with support for the tasks extension.

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

Enables developers to build and deploy secure, typed Model Context Protocol servers with tools, resources, prompts, bearer-token authentication, per-tool scopes, rate limiting, and health probes over Streamable HTTP.

Acts as a bridge between standard REST/OpenAPI web APIs and the Model Context Protocol, dynamically converting REST endpoints into MCP tools for LLM clients like Cursor, Claude Desktop, and n8n.

An MCP server that turns a one-sentence idea into working, tested code using a pipeline of six AI agents, with optional deployment.