Skip to content

Adding installation instructions for env var usage #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Adding installation instructions for env var usage #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,29 @@ Then, configure your server definition to reference your local clone. For exampl
}
```

### Installation steps using environment variables

Some AI clients allow for accessing environment variables within MCP configurations. In AI clients where this is supported, you can configure your MCP server to read from an environment variable like `MCP_LD_TOKEN` as follows:

```json
{
"mcpServers": {
"launchdarkly": {
"command": "npx",
"args": [
"-y", "--package", "@launchdarkly/mcp-server", "--", "mcp", "start",
"--api-key", "$LD_ACCESS_TOKEN"
],
"env": {
"LD_ACCESS_TOKEN": "MCP_LD_TOKEN"
}
}
}
}
```

This won't work in AI clients (such as Cursor) which don't support accessing environment variables directly within MCP configurations. As a workaround, you can invoke a local script from your MCP configuration. See [here](https://github.com/launchdarkly/mcp-server/issues/26#issuecomment-3064419507) for an example.

<!-- Start Requirements [requirements] -->
## Requirements

Expand Down