# AgentX [Verified owner] [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://www.agentxhq.com/mcp  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/agentx

## Description
Connect your AI assistant to AgentX, a cloud console for a fleet of AI coding agents (Claude Code, Codex CLI, Grok CLI) that run on your own machines through the AgentX daemon. Remote MCP server, OAuth. Manage connections at https://www.agentxhq.com/settings/connected.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "agentx": {
    "url": "https://www.agentxhq.com/mcp"
  }
}
```

## Documentation

## What AgentX MCP server does

AgentX connects an AI assistant to the AgentX cloud console and the coding-agent fleet registered with it. The fleet can include Claude Code, Codex CLI, and Grok CLI processes running on machines you control. AgentX acts as the MCP connection between the assistant and that remote console, allowing the assistant to work with the connected agent environment.

The main use case is centralized access to multiple coding agents. Instead of treating each local agent as an isolated assistant integration, AgentX provides a cloud-console layer for managing connections to agents running across your own machines.

## How it works

The coding agents run locally through the AgentX daemon. AgentX provides the remote MCP service that connects an AI assistant to the cloud console, while the daemon represents the machines and agents participating in the fleet. This separates where the coding agents execute from where the MCP connection is hosted.

Authentication uses OAuth. After authorization, the assistant can use the AgentX connection to work with the configured fleet through the remote service. The AgentX console is responsible for managing the connections between the cloud account and the machines running the daemon.

This architecture fits teams or developers who operate more than one coding-agent process and want an assistant-facing connection to the fleet rather than a direct, per-machine MCP setup.

## Setup and configuration

Start from the AgentX MCP page at https://www.agentxhq.com/mcp and use the remote connection flow for an MCP-capable assistant. OAuth handles authorization for the connection. Connected accounts and agent connections can be managed at https://www.agentxhq.com/settings/connected.

The machines that provide coding agents need to run the AgentX daemon. The supported agent types named for the fleet are Claude Code, Codex CLI, and Grok CLI. Configuration therefore involves both the remote MCP authorization and the local machines that host the agents.

## Tools and capabilities

- Connect an AI assistant to the AgentX cloud console over remote MCP.
- Authenticate the connection with OAuth.
- Manage connections to machines running the AgentX daemon.
- Work with fleets containing Claude Code, Codex CLI, and Grok CLI agents.
- Keep coding-agent execution on the user’s own machines while exposing the fleet through the cloud console.

## Limitations and notes

AgentX depends on the AgentX daemon for the machines and coding agents it manages. It is designed around a remote MCP and OAuth connection, rather than a local stdio process. The supported fleet integrations identified for this listing are Claude Code, Codex CLI, and Grok CLI. Access to an agent depends on that agent being connected through the AgentX daemon and available in the AgentX console.

_Full upstream README: https://allmcps.com/mcp/agentx/readme_