"MTA" matching MCP servers:

Enables AI to dynamically discover and invoke any Cin7 Core API endpoint using three generic tools (list, describe, invoke) plus a bug-report tool, covering the entire API surface without predefined endpoints.

Read-only Python MCP server for TA-Lib indicator discovery and computation.

Agency-grade MCP server for WordPress Elementor — multi-site management for 120+ WordPress sites with safe edits (backup + auto-rollback + post-write verification), template export/import, global widget detection, CSS flush, WP-CLI escape hatch, and headless Chrome screenshots. 34 tools across pages, widgets, templates, bulk find/replace, and fleet operations.

Enables running bpy Python code in an already-open Blender instance, with tools for health checks, scene info, and viewport screenshots.

An MCP server that connects AI assistants to a local Wolfram Engine, enabling symbolic math, numerical analysis, and data visualization through Wolfram Language. It provides secure expression filtering, client authentication, and supports both local stdio and HTTP transports.

Enables safe, authenticated access to GitHub via local GitHub CLI, providing read-only operations such as listing repositories, issues, and pull requests.

infomaniak-mcp-agent lets Claude (or any MCP client) drive a real Infomaniak account end-to-end through 54 tools — web hosting, mail, kDrive, domains, DNS, DNSSEC, FTP/SSH users, AI catalogue and more. Every destructive operation goes through a strict two-phase commit (plan + single-use confirmation token) so the agent can never silently mutate your account. Open Source

Enables read-only access to FileMaker databases through the Data API, allowing users to retrieve records, analyze metadata, search across layouts, and infer relationships while maintaining data security.

Headless MCP server for Eclipse MAT that enables analyzing Java heap dumps using built-in commands, OQL queries, and predefined reports.

Model Context Protocol server for the MetaTrader 4/5 build pipeline, enabling LLM-driven compilation, deployment, backtesting, and log tailing without UI interaction.

Enables LLM agents to compile, deploy, backtest, and analyze MetaTrader 4/5 MQL sources without touching the MetaTrader UI, leveraging the build pipeline.

A tool that dynamically generates and configures MCP servers by automatically creating necessary directories and files according to user specifications.

A Model Context Protocol server that enables AI models to interact with GitHub's API, allowing for repository creation and management with descriptions, topics, and website URLs through natural language commands.

Enables AI-driven batch refactoring of Movable Type content via the MT Data API using natural language instructions. It provides a secure workflow featuring automated backups, visual diff reports, and rollback capabilities for safe HTML transformations.

An MCP server for ServiceNow that supports multi-factor authentication via real browser (Playwright) and provides tools for reading, writing, and managing ServiceNow artifacts with safety guards.

A meta API Gateway server that works with the Model Context Protocol (MCP), enabling AI assistants to connect to any API and access real-world data sources through standardized MCP tools.

Enables agents to generate typed client code from OpenAPI, GraphQL, Protobuf, and SQL specs using MetaEngine's code-generation platform.

Enables interaction with Mia-Platform Console through the Model Context Protocol, supporting machine-to-machine authentication and personal credentials for managing resources.

A sample implementation of a Model Context Protocol server using Next.js and the Vercel MCP Adapter, allowing developers to create AI assistants with custom tools and resources.

Enables an MCP server to gate tools/call requests by requiring a per-send channel-policy attestation for outbound actions, checking ROPE-lite origin tags on sensitive arguments, and returning SEP-2643-shaped structured denials with retry handles and remediation hints when a call is blocked. It logs client-asserted audit context (such as turnId and userIntent) for correlation across allowed and denied calls, but never uses that receipt for allow/deny decisions.