You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-51Lines changed: 25 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,76 +4,53 @@ MCP (Model Context Protocol) server that provides AI assistants with access to t
4
4
5
5
## Quick Start
6
6
7
-
Add to your MCP client configuration (e.g., Claude Desktop):
7
+
**1. Authenticate:**
8
+
9
+
```bash
10
+
npx @dopplerhq/mcp-server login
11
+
```
12
+
13
+
**2. Add to your MCP client configuration (e.g., Claude Desktop):**
8
14
9
15
```json
10
16
{
11
17
"mcpServers": {
12
18
"doppler": {
13
19
"command": "npx",
14
-
"args": ["-y", "@dopplerhq/mcp-server"],
15
-
"env": {
16
-
"DOPPLER_TOKEN": "<your-doppler-token>"
17
-
}
20
+
"args": ["-y", "@dopplerhq/mcp-server"]
18
21
}
19
22
}
20
23
}
21
24
```
22
25
23
-
See [Service Tokens](https://docs.doppler.com/docs/service-tokens) to create a token.
26
+
### With Service Token
24
27
25
-
### Alternative: CLI Authentication (No Token in Config)
26
-
27
-
If you have the [Doppler CLI](https://docs.doppler.com/docs/cli) installed, you can use your CLI session instead of a service token. This keeps credentials out of your config file entirely.
28
-
29
-
**Prerequisites:**
30
-
31
-
1. Install the Doppler CLI
32
-
2. Run `doppler login` (creates a global/root session stored in your OS keychain)
33
-
3. Create a Doppler project to store your `DOPPLER_TOKEN` for the MCP server
34
-
35
-
**Configuration:**
28
+
Alternatively, use a service token instead of logging in:
36
29
37
30
```json
38
31
{
39
32
"mcpServers": {
40
33
"doppler": {
41
-
"command": "doppler",
42
-
"args": [
43
-
"run",
44
-
"--project",
45
-
"mcp-server-tokens",
46
-
"--config",
47
-
"dev",
48
-
"--",
49
-
"npx",
50
-
"-y",
51
-
"@dopplerhq/mcp-server",
52
-
"--project",
53
-
"my-app",
54
-
"--read-only"
55
-
]
34
+
"command": "npx",
35
+
"args": ["-y", "@dopplerhq/mcp-server"],
36
+
"env": {
37
+
"DOPPLER_TOKEN": "<your-doppler-token>"
38
+
}
56
39
}
57
40
}
58
41
}
59
42
```
60
43
61
-
**How it works:**
62
-
63
-
-`doppler run --project mcp-server-tokens --config dev` fetches secrets (including `DOPPLER_TOKEN`) from the specified Doppler project and injects them as environment variables
64
-
- The MCP server receives `DOPPLER_TOKEN` and uses it to access the Doppler API
65
-
-`--project my-app --read-only` on the MCP server scopes what the LLM can access
44
+
See [Service Tokens](https://docs.doppler.com/docs/service-tokens) to create a config-scoped token.
0 commit comments