@letta-ai/letta-code 0.31.1 → 0.31.2
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/dist/mcp-client.js +2 -2
- package/dist/mcp-client.js.map +1 -1
- package/dist/types/hooks/executor.d.ts.map +1 -1
- package/dist/types/tools/impl/shell-launchers.d.ts +3 -1
- package/dist/types/tools/impl/shell-launchers.d.ts.map +1 -1
- package/letta.js +400 -168
- package/package.json +1 -1
- package/skills/using-server-mcp/SKILL.md +36 -0
package/package.json
CHANGED
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: using-server-mcp
|
|
3
|
+
description: Uses MCP servers that are already connected to the current Letta Cloud agent through server-side MCP associations. Load when the user asks to use an associated MCP server, list an agent's MCP servers or MCP tools, run an MCP tool connected in ADE/chat, or mentions server-side MCP, agent MCP, or `letta server-mcp`.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Using Server-Side MCP
|
|
7
|
+
|
|
8
|
+
Use this skill when the current Letta Cloud agent has MCP servers connected in Letta and you need to discover or run their tools.
|
|
9
|
+
|
|
10
|
+
## Workflow
|
|
11
|
+
|
|
12
|
+
1. List connected MCP servers:
|
|
13
|
+
|
|
14
|
+
```bash
|
|
15
|
+
letta server-mcp list
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
2. Pick the relevant `id` from the JSON output, then list its tools:
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
letta server-mcp tools <mcp-server-id>
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
3. Pick a tool `id`, inspect the tool name/description, and run it with a JSON object:
|
|
25
|
+
|
|
26
|
+
```bash
|
|
27
|
+
letta server-mcp run <mcp-server-id> <tool-id> --args '{"key":"value"}'
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
## Rules
|
|
31
|
+
|
|
32
|
+
- Prefer the `letta server-mcp ...` CLI over model-facing MCP tools. There is no dedicated `agent_mcp` tool.
|
|
33
|
+
- Do not ask for an agent ID unless the user wants another agent. In normal Letta Code sessions the CLI reads `LETTA_AGENT_ID`/`AGENT_ID` from the environment.
|
|
34
|
+
- Treat command output as JSON. Summarize relevant results instead of pasting large raw payloads.
|
|
35
|
+
- If no servers are listed, tell the user to connect an MCP server to the agent in the MCP servers page first.
|
|
36
|
+
- This only works for signed-in Letta Cloud agents with server-side MCP support. It is separate from local MCP transport testing or converting arbitrary MCP servers into skills.
|