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
title: Quick start
description: Launch every tuls server in one place.
Every server speaks MCP over stdio. These commands are safe to run from a
terminal to validate behavior before wiring up a client.
```bash
tuls filesystem /absolute/path/to/project \
--allow filesystem.read
```
```bash
tuls filesystem /absolute/path/to/project \
--allow filesystem.read \
--allow filesystem.write
```
```bash
tuls fetch \
--allow network.fetch
```
The fetch defaults are intentionally restrictive:
```text
--robots respect
--network public
```
```bash
tuls memory \
--memory-file /absolute/path/to/memory.jsonl \
--allow memory.read \
--allow memory.write
```
```bash
tuls shell /absolute/path/to/project \
--allow process.execute
```
```bash
tuls skills /absolute/path/to/project \
--allow skills.read
```
```bash
tuls agents /absolute/path/to/project \
--allow agents.run
```
::: tip Next
Every launch above grants the minimum capability for its server. See the
[capability policy](./capability-policy) to understand how `--allow` and
`--deny` shape the tool surface, or jump to a specific
[server reference](../servers/).
:::