# AgentsMesh MCP server

> Synchronizes rules, skills, and MCP servers across multiple AI coding tools using a single canonical configuration source.

- Repository: https://github.com/sampleXbro/agentsmesh
- Page: https://hostedmcp.org/servers/samplexbro/agentsmesh
- Transport: stdio
- Stars: 29
- License: MIT

## Install

### Claude Code

```sh
claude mcp add agentsmesh -- npx -y agentsmesh
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "agentsmesh": {
      "command": "npx",
      "args": [
        "-y",
        "agentsmesh"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "agentsmesh": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agentsmesh"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"agentsmesh","type":"stdio","command":"npx","args":["-y","agentsmesh"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "agentsmesh": {
      "command": "npx",
      "args": [
        "-y",
        "agentsmesh"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add agentsmesh -- npx -y agentsmesh
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.agentsmesh]
command = "npx"
args = ["-y", "agentsmesh"]
```

### Gemini CLI

```sh
gemini mcp add -s user agentsmesh npx -- -y agentsmesh
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "agentsmesh": {
      "command": "npx",
      "args": [
        "-y",
        "agentsmesh"
      ]
    }
  }
}
```

## FAQ

### Can I import my existing AI tool configurations?

Yes, the import command allows you to pull existing configurations from various tools back into the central AgentsMesh source without losing data.

### How does AgentsMesh prevent configuration drift?

You can use the check command in your CI pipeline to fail builds if the generated tool-specific files drift from the central source.