@mrrlin-dev/external-agents 0.2.5 → 0.2.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -86,9 +86,32 @@ Open the local dashboard with `external-agents ui` and you'll get a page like:
|
|
|
86
86
|
|
|
87
87
|
Once installed, add one block to your MCP client config.
|
|
88
88
|
|
|
89
|
-
The package ships a dedicated `external-agents-mcp` binary — the MCP server entry — so client configs are plain command lines with no args.
|
|
89
|
+
The package ships a dedicated `external-agents-mcp` binary — the MCP server entry — so client configs are plain command lines with no args. **Both Claude Code and Codex expose a one-liner** for this; you should never have to hand-edit config files unless you want to.
|
|
90
|
+
|
|
91
|
+
### Claude Code
|
|
92
|
+
|
|
93
|
+
```bash
|
|
94
|
+
claude mcp add external-agents external-agents-mcp
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
(Uses the native `claude mcp add <name> <command>` — the CLI writes the block into `~/.claude.json` for you and Claude Code picks it up on next start.)
|
|
98
|
+
|
|
99
|
+
### Codex
|
|
100
|
+
|
|
101
|
+
```bash
|
|
102
|
+
codex mcp add external-agents -- external-agents-mcp
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
(Uses the native `codex mcp add <name> -- <command>` — the CLI writes `[mcp_servers.external-agents]` into `~/.codex/config.toml`.)
|
|
106
|
+
|
|
107
|
+
### Cursor
|
|
108
|
+
|
|
109
|
+
Settings → MCP → Add server → command `external-agents-mcp`, no args.
|
|
110
|
+
|
|
111
|
+
### Manual (any other client)
|
|
112
|
+
|
|
113
|
+
If your MCP client doesn't have a one-liner, the config block is:
|
|
90
114
|
|
|
91
|
-
**Claude Code** (`~/.claude.json`):
|
|
92
115
|
```json
|
|
93
116
|
{
|
|
94
117
|
"mcpServers": {
|
|
@@ -100,14 +123,15 @@ The package ships a dedicated `external-agents-mcp` binary — the MCP server en
|
|
|
100
123
|
}
|
|
101
124
|
```
|
|
102
125
|
|
|
103
|
-
|
|
126
|
+
or TOML equivalent:
|
|
127
|
+
|
|
104
128
|
```toml
|
|
105
129
|
[mcp_servers.external-agents]
|
|
106
130
|
command = "external-agents-mcp"
|
|
107
131
|
args = []
|
|
108
132
|
```
|
|
109
133
|
|
|
110
|
-
|
|
134
|
+
No publishing step — the MCP server is just `external-agents-mcp` on your PATH once you `npm i -g @mrrlin-dev/external-agents`. Nothing to host, nothing to expose over the network; it's a stdio-transport MCP server that runs locally, same as any other npm-installed CLI.
|
|
111
135
|
|
|
112
136
|
Your primary agent now has these low-level tools (build your own exec/review flows on top):
|
|
113
137
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mrrlin-dev/external-agents",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.6",
|
|
4
4
|
"description": "One MCP server for every LLM you talk to — direct-API dispatcher across Gemini, DeepSeek, Groq, OpenRouter, Cerebras, and more. Part of mrrlin.com.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "server.js",
|