apexe 0.6.0

Outside-In CLI-to-Agent Bridge
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112

# apexe Quick Start

> Turn any CLI tool into an AI-callable MCP service in 30 seconds.

## Install

```bash
git clone https://github.com/aiperceivable/apexe.git
cd apexe
cargo install --path .
apexe --version
```

## 30 seconds: Scan, Serve

```bash
apexe scan git
apexe serve
```

## Claude Desktop Integration

```bash
apexe serve --show-config claude-desktop
```

Copy the output into `~/Library/Application Support/Claude/claude_desktop_config.json`, then restart Claude Desktop.

The snippet reproduces whatever else you put on that command line, so pass the
flags you intend to serve with — above all `--modules-dir` if you scanned
somewhere other than `~/.apexe/modules`, since a client that launches `apexe
serve` without it finds no tools:

```bash
apexe serve --show-config claude-desktop --modules-dir /srv/apexe/modules --acl ~/.apexe/acl.yaml
```

Credentials (`--auth-token`, `--jwt-secret`) are never written into the
snippet — set those on the client side.

## Cursor Integration

```bash
apexe serve --show-config cursor
```

Add the output to Cursor's MCP settings.

## HTTP Mode with Explorer UI

```bash
apexe serve --transport http --port 8000 --explorer
```

Open `http://127.0.0.1:8000` in a browser to explore available tools.

## A2A Agent Server

Serve the same scanned tools as an A2A agent instead of (or alongside) MCP:

```bash
apexe a2a
```

`apexe a2a` shares governance (ACL, logging, approval) with `apexe serve` — see [User Manual §10](user-manual.md#10-mcp-server) and §11 for details.

## What happened?

1. `apexe scan git` ran git's `--help`, parsed man pages, and checked shell completions.
2. Generated `~/.apexe/modules/git.binding.yaml` (JSON Schema for every subcommand).
3. Generated `~/.apexe/acl.yaml` (readonly commands allowed, destructive commands denied).
4. `apexe serve` started an MCP server on stdio, exposing all scanned tools.

## Scan more tools

```bash
apexe scan ls curl jq
```

## See what you have

```bash
apexe list
apexe list --format json
```

## Next steps

```bash
# Deep scan with 3 levels of subcommands
apexe scan git --depth 3

# HTTP server for remote agents
apexe serve --transport http --port 8000

# SSE transport (deprecated upstream -- prefer --transport http)
apexe serve --transport sse --port 8000

# Also generate Claude Skills (.claude/skills/<id>/SKILL.md) per module
apexe scan git --skills-dir ./out

# Observability: /metrics (Prometheus) + /usage (HTTP/SSE only)
apexe serve --transport http --metrics

# Initialize a config file for customization
apexe config --init

# View resolved configuration
apexe config --show
```

See [User Manual](user-manual.md) for full documentation.