Discover +702 AI Agents apps & tools

Pros: Executes Cypher queries directly against Neo4j instances. MCP-compatible server for assistant clients such as Claude Desktop. Open-source project recognized within the MCP community.

Cons: Supports only Neo4j databases, not other graph engines. Requires developer setup and a recent Go toolchain. Model-generated queries require human review and permission controls.

Pros: Native MCP compatibility, integrates with clients like Claude Desktop. Focuses on localization, prioritizing cultural and contextual fit. Open-source codebase enables customization and pipeline integration.

Cons: Requires external LLM access via API key for core processing. Deployment needs Node.js and repository configuration. Outputs should undergo human editorial review for high-stakes releases.

Pros: Acts as an MCP server, letting AI agents read and modify project files. Supports OpenAI and Anthropic backends for provider choice. Processes JSON and YAML localization formats directly. CLI design fits terminal integration and build pipelines.

Cons: Requires an MCP-compliant host and Node.js runtime. Localization quality depends on chosen LLM and prompt design. Focused on structured files; limited for unstructured text workflows.

Pros: Native MCP integration allows AI hosts to read and update localization data. Open-source design enables self-hosting and customization for pipelines. Preserves key-level context and technical tone in model suggestions.

Cons: Not a standalone translation app; requires an MCP-compatible host. Requires a Node.js environment and basic developer setup. Translation quality varies with the chosen underlying language model.

Pros: Exposes EPM REST API actions to LLMs for direct operational use. Supports business-rule execution and cell-level data queries via prompts. Job-monitoring endpoints let users verify background process status. Uses environment variables for secure credential handling during integration.

Cons: Requires an MCP host and Node.js 18+, adding technical setup. Can modify EPM data when credentials allow, so needs governance. Designed for Oracle EPM Cloud REST APIs, not on-premises versions.

Pros: Combines multiple MCP servers within a single repository for consolidated deployment. Open-source codebase allows inspection and security auditing. Cross-platform support with Node.js for Windows, macOS, and Linux. Extensible via Model Context Protocol to add custom server modules.

Cons: Requires Node.js and manual repository configuration for setup. Google Search server needs a user-supplied API key. Local shell and file access require careful permission management. Geared toward developers, less suitable for non-technical users.

Pros: Uses AppleScript for direct, native access to the Things 3 database. Runs locally, keeping task data on the user's machine. Implements the MCP standard for compatibility with MCP clients.

Cons: Requires macOS and the Things 3 desktop app to operate. Setup assumes familiarity with MCP hosts and desktop automation. Current focus is on reading, searching, and creating tasks rather than full item lifecycle.

Pros: Exposes in-code tasks through the Model Context Protocol. Supports creating, updating, and filtering TODO comments. Node.js implementation is open and easy to inspect. Integrates with MCP hosts such as Claude Desktop.

Cons: Requires an MCP host and VS Code to operate. Relies on file-system permissions granted to the server. Focused on comment-based tasks, not broad code edits.

Pros: Direct MCP integration lets LLMs query live NBA stats via API. Open-source codebase available for inspection and community contributions. Focused, lightweight server designed for local configuration and deployment.

Cons: Requires a balldontlie.io API key for authenticated requests. Depends on third-party API data for factual accuracy. Requires Node.js and MCP-compatible host setup.

Pros: Native MCP tools let LLMs read, process, and write localization data. Context-aware translations use surrounding code to reduce literal errors. Handles common localization formats such as JSON and YAML. Open-source and extensible for integration into CI/CD pipelines.

Cons: Requires an MCP-compatible host and a Python environment. Translation quality depends on the underlying language model used. Intended for developer workflows, not non-technical GUI users.

Pros: Exposes blend_links and localize_content to MCP clients for direct invocation. Combines multiple URLs into a single analysis context for the connected model. Extracts metadata and OpenGraph tags to enrich contextual signals. Open-source repository enables community extensions and custom tool development.

Cons: Requires an MCP-compatible client and runtime setup before use. Not designed for large-scale website scraping or sitewide crawling. Best suited to technical users familiar with GitHub deployments.

Pros: Exposes local file CRUD to MCP clients. Enables terminal command execution from assistant. Provides Git tools for status, branches, and commits. Open-source codebase available for auditing and customization.

Cons: Grants significant local system access requiring monitoring. Needs Node.js and an MCP-compatible client. Targeted at technically proficient users, not beginners.

Pros: BLAKE3 hashing enables cryptographic verification of graph state. ACID-compliant redb backend supports transactional data integrity. MCP bridge, CLI, and HTTP API enable programmatic integrations. Local-first binary avoids mandatory cloud processing for core logic.

Cons: Alpha release may include breaking changes; stability is evolving. No preloaded knowledge; explicit ingestion required before use. Developer-oriented setup, requires familiarity with MCP and tooling.

Pros: Exposes Genesys Cloud data to LLMs via the Model Context Protocol. Returns transcripts with speaker labels and timestamps. Provides call-quality metrics such as MOS, jitter, and packet loss. Configurable for all Genesys Cloud regions and MCP clients.

Cons: Requires Genesys Cloud OAuth credentials and explicit region configuration. Depends on underlying API and transcription quality; needs validation. Runs via Node.js npx, requiring technical setup.

Pros: Implements Model Context Protocol for agent compatibility (Claude Desktop, Cursor).. Exposes localization functions as discoverable, callable tools for agents.. TypeScript/Node.js codebase fits standard development environments.. Retains legacy API, useful for studying earlier Hotplex integrations..

Cons: Localization output depends on connected LLMs, not built-in translation.. Marked as a legacy project after the unified Hotplex runtime release.. Project overview does not specify data-handling or retention controls..

Pros: Terminal and Tauri desktop interfaces for different workflows. Supports Anthropic, OpenAI, and Codex provider selection. Persistent session management retains chat history across restarts. No Node.js dependency; runs on the .NET runtime.

Cons: Generated code requires developer review and testing. Users must supply API keys for external providers. CLI use requires the .NET runtime installed. Command execution requires careful permission handling.