setup-credentials
/setup-credentials
Set up or update the Tulip MCP plugin's credentials. Use when the server reports missing/invalid credentials, when the user says the plugin isn't authenticated, or right after installing the plugin. Copies the user's existing .env into the plugin's persistent data directory so it survives updates.
- Author
- tulip ↗
- Repository
- tulip-mcp ↗
- Licence
- Apache-2.0
- Last repository change
- 14.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 14.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Set up or update the Tulip MCP plugin's credentials. Use when the server reports missing/invalid credentials, when the user says the plugin isn't authenticated, or right after installing the plugin. Copies the user's existing .env into the plugin's persistent data directory so it survives updates.
Triggers from the description
Original author description
Set up or update the Tulip MCP plugin's credentials. Use when the server reports missing/invalid credentials, when the user says the plugin isn't authenticated, or right after installing the plugin. Copies the user's existing .env into the plugin's persistent data directory so it survives updates.
How it works
- Keywords
- Overview
- What credentials are needed
- Prerequisite: the user needs an .env file
- Resolving the data directory path
- Steps
- Notes
SKILL.md preview
--- name: setup-credentials description: "Set up or update the Tulip MCP plugin's credentials. Use when the server reports missing/invalid credentials, when the user says the plugin isn't authenticated, or right after installing the plugin. Copies the user's existing .env into the plugin's persistent data directory so it survives updates." --- # Set up Tulip MCP credentials ## Keywords setup credentials, configure plugin, .env, not authenticated, login failed, missing api key, first run, install setup, credentials not found, reconnect tulip, api key, api secret, base url, workspace id ## Overview The Tulip MCP plugin reads credentials from a `.env` file in its persistent data directory, which survives plugin updates. This skill helps the user place that file. **Important — never ask the user to paste credentials into this chat.** Credentials (API keys, passwords) must not be typed into the conversation. This skill asks only for the *path* to the user's existing `.env` file and copies it into place. Do not read, cat, or print the file's contents at any point. ## What credentials are needed The `.env` file requires these values: | Variable | Required | Description | |---|---|---| | `TULIP_API_KEY` | Yes | API key from your Tulip instance | | `TULIP_API_SECRET` | Yes | Corresponding API secret | | `TULIP_BASE_URL` | Yes | Your instance URL, e.g. `https://your-instance.tulip.co` | | `TULIP_WORKSPACE_ID` | Account keys only | Usually `DEFAULT` — not needed for Workspace API keys | API keys are created in your Tulip instance under **Settings → API Keys**. Workspace API keys (an enterprise feature) do not require `TULIP_WORKSPACE_ID`. Account API keys do. ## Prerequisite: the user needs an .env file If the user does not already have a `.env` file, point them to the template `env.example` in the plugin repo. Tell them to copy it to a file named `.env`, fill in their values in a text editor, and save it somewhere they can find (e.g. their Documents folder). Do not ask them to share the values here. ## Resolving the data directory path The plugin's persistent data directory is derived from the plugin identifier. For standard marketplace installs, the identifier is `tulip@tulip-marketplace`, which resolves to: ``` ~/.claude/plugins/data/tulip-tulip-marketplace/ ``` To confirm the correct path at runtime, read `~/.claude/plugins/installed_plugins.json` and find the key that starts with `tulip@`. The data directory name is that key with every non-alphanumeric character replaced by a hyphen. For example, `tulip@tulip-marketplace` becomes `tulip-tulip-marketplace`. ## Steps Commands below are given for POSIX shells (macOS, Linux, and Git Bash on Windows) and for PowerShell. Pick the set that matches the user's shell. 1. Discover the data directory by reading `~/.claude/plugins/installed_plugins.json` with the Read tool. Find the key matching `tulip@*` in the `plugins` object. Replace every non-alphanumeric character in that key with `-` to get the directory name. The full path is `~/.claude/plugins/data/<directory-name>/`. 2. Ask the user for the full path to their filled-in `.env` file. Example prompt: "What's the full path to your Tulip `.env` file? (e.g. `/Users/you/Documents/tulip.env` or `C:\Users\you\Documents\tulip.env`)" 3. Confirm the file exists before copying (list metadata only, never contents): ```bash ls -la "<user-provided-path>" ``` ```powershell Get-Item "<user-provided-path>" | Select-Object FullName, Length, LastWriteTime ``` If it does not exist, tell the user and ask again. Do not proceed. 4. Copy it into the plugin's persistent data directory, creating the directory if needed: ```bash mkdir -p ~/.claude/plugins/data/<directory-name> cp "<user-provided-path>" ~/.claude/plugins/data/<directory-name>/.env chmod 600 ~/.claude/plugins/data/<directory-name>/.env ``` ```powershell New-Item -ItemType Directory -Force -Path "$HOME\.claude\plugins\data\<directory-name>" Copy-Item "<user-provided-path>" "$HOME\.claude\plugins\data\<directory-name>\.env" ``` The `chmod` step restricts the file to the owner and applies to POSIX shells only. On Windows, the file inherits the user profile's permissions, which are already limited to that user — tell the user this rather than trying to set an ACL. Never open, cat, or print the file's contents. 5. Confirm the copy landed (metadata only): ```bash ls -la ~/.claude/plugins/data/<directory-name>/.env ``` ```powershell Get-Item "$HOME\.claude\plugins\data\<directory-name>\.env" | Select-Object FullName, Length, LastWriteTime ``` 6. Tell the user to reload the plugin so the server picks up the credentials: "Credentials are in place. Run `/reload-plugins` (or restart Claude Code) to connect." ## Notes - Because the file lives in the persistent data directory, it survives future plugin updates — the user does this once (until their credentials change). - If the user later changes credentials, re-run this skill with the new file. - If the user is running the server standalone (not as a plugin), a `.env` in the repo root is used instead — this skill is only needed for plugin installs. - The `ENABLED_TOOLS` environment variable in `.env` controls which tools are active. Default is `read-only`, which exposes 30 of the 71 tools. To enable write tools, set `ENABLED_TOOLS=read-only,write` or a list of specific categories, types, or tool names. See `env.example` for full options.
Versions
The database has no other skills named setup-credentials.
Database snapshot: 13.11.2026 · package version 48533c7e587e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100setup
Set up the OKF MCP plugin — outputs a guide for the user to create their ~/.okf/credentials file with their OAuth2 client id/secret. Use when first enabling the plugin, when headersHelper fails with "Missing credentials", or when the user says "setup okf". - 100output-credentials-env-vars
Wire encrypted credentials to environment variables using the credential: convention. Use when setting up LLM provider keys (ANTHROPIC_API_KEY, OPENAI_API_KEY) or any env var that should come from encrypted credentials. - 100output-credentials-init
Initialize encrypted credentials for an Output.ai project. Use when setting up credentials for the first time, adding environment-specific credentials, or adding per-workflow credentials. - 100configure
Configure the claude-lark-plugin by managing ~/.claude/channels/lark/.env. Use when the user asks to configure, setup, or change Lark/Feishu settings or credentials. - 100gb-setup
Configure GrowthBook API credentials and the trusted app origin so the other skills can run and link to the UI. Use when the user says "set up growthbook", "configure my api key", "growthbook isn't working", "where do I put my key", or when another skill emits an error pointing… - 84setup
Check or set up the sql-server read-only MCP server: Node.js, the config file against its schema, the server copy in the plugin data directory, and a claude mcp add command per environment that names credentials by reference. Use when: 'set up sql-server', 'register a database…