"Information about Autotask software or service" matching MCP servers:

A persistent 24/7 background daemon that aggregates all downstream MCP servers into one unified connection and layers on a real-time notification gateway so AI agents can receive events from X/Twitter, Slack, Email, and webhooks.

A Model Context Protocol service that enables agent authentication and integration with TrustGo platform, providing access to real-time data like price, sigma score, and mindshare bubble analytics.

Enables agents to discover and invoke travel recommendations with partner-specific caps and exclusions via MCP JSON-RPC.

Enables users to generate complete, production-ready software projects from simple ideas by coordinating 8 specialized AI agents through the Model Context Protocol.

A service for managing ESP8266/NodeMCU IoT devices that provides both REST/WebSocket APIs and implements the Model Context Protocol for AI assistant integration.

Dual-interface MCP server that exposes declarative tools and reusable skills via standard MCP protocol and provides a REST API for authoring them.

An interface enabling high-frequency communication between AI tools (like Cursor and Windsurf) and users, allowing for option selection and information gathering through CLI, Web, or PyQt interfaces.

An MCP server that enables AI models to access user geolocation information through EdgeOne Pages Functions.

A professional AI agent system that provides 10+ specialized agents and 25+ MCP tools to support development workflows in Cursor IDE, with dual LLM mode support (built-in and DeepSeek API).

Integrates live Screeps game data into AI development workflows, providing comprehensive tools for room operations, market analysis, and user management. It enables AI agents to monitor game status and interact with the game world through the Model Context Protocol.

A Model Context Protocol server for the resQ emergency response system that integrates with digital twin simulations and coordination engines. It allows users to trigger simulations, generate deployment strategies, and monitor real-time drone status for incident response analysis.

Declarative MCP runtime over IDF artifacts. Tool descriptions carry invariants, lifecycle, irreversibility, and role scopes.

Enables AI agents to execute provider tools through a self-hostable gateway with scoped keys, permissions, and accounting reservations.

A git-backed MCP server that centrally manages AI agent skills, tools, and knowledge with role-based access, change requests, and a remote OAuth 2.1 endpoint.

Enables AI-powered multi-provider routing and chat through an MCP interface, with smart fallback, persistent sessions, and learning from historical performance.

Enables AI agents to respond to users with live, persistent, interactive web apps served at a single URL that evolve in place as the conversation continues. It exposes UI generation and evolution tools over MCP so agent responses can include clickable buttons and streaming interfaces alongside chat replies.

Enables connections to Azure AI Agents within any MCP client, allowing users to leverage Azure AI Foundry's models and knowledge tools like Azure AI Search and Bing Web Grounding through a conversational interface.

The coordination layer for AI agent networks, providing persistent memory, task management, inter-agent messaging, and human oversight through native MCP tools.

Governance and session management layer for AI-assisted software development; enables agent binding, session tracking, and structured code review within the HestAI ecosystem.

Enables Claude Code to delegate software-engineering tasks to OpenCode agents working in the same workspace.

Enables AI agents to submit software tools to the Altimateguide directory for editorial review through a single submit_tool operation. Submissions are queued as pending and never published automatically.

Enables AI agents to search the public pages of Soft98, P30Download, Downloadly and VGDL for software and games, returning metadata only — name, version, size, category, date, short description, system requirements and the item page URL. It is read-only and never downloads files, returns file links, passwords or crack notes.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

Local, zero-token event triggers for Claude Code, Codex, OpenCode and ZCode: when CI fails, a training run finishes, a service goes down or NVDA crosses your price, your agent wakes up in your conversation—even if closed.

Provides AI assistants with real-time access to the AGNO framework documentation by enabling them to browse, search, and fetch documentation pages. This server allows users to query information about AGNO's Agents, Teams, and Workflows directly through MCP-compatible clients.

Enables selecting a saved Codex or Claude Code session from the same PC and importing its recent context into the other tool, so work can continue across clients with source and omission information.

Hand tasks from Claude Code, Cursor or Codex to a personal agent through a folder of markdown notes, and read the reply back. Runs on your computer: no hosted service, no account, no telemetry. Eight tools: send, status, list, read, wait, rules and the agent's inbox. Optional email, Telegram or Slack heads-up (outgoing only, off by default). Refuses requests that look like passwords or keys.

Coordinates Codex and Antigravity CLI for a structured software development workflow with workspace authorization, Git-based verification, and acceptance criteria.

۩ Plan your projects with THC! MLLM planning harness for Software Engineering, modifiable for other purposes, released as an MCP server. Bring your own API keys. Open-Source now, my dear! :D

Enables AI tools to drive a hosted, headless Chromium browser over HTTP — navigating, clicking, typing, and reading pages through structured accessibility snapshots — without installing a browser locally or running npx on each machine. It runs as a single authenticated Render web service that any MCP client can connect to at a shared HTTPS endpoint.