> For the complete documentation index, see [llms.txt](https://docs.kinesis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinesis.network/mcp/connect/claude-code.md).

# Claude Code

Connect Claude Code to Kinesis with a command, then sign in from /mcp.

Use Claude Code to inspect projects, deploy apps and operate Kinesis from your terminal. You need Claude Code installed and a [Kinesis account](https://portal.kinesis.network/signup).

## Connect with your Kinesis account

{% stepper %}
{% step %}

### Add the server

Run this in your terminal:

```bash
claude mcp add --transport http --scope user kinesis "https://mcp.kinesis.network/mcp?mode=all"
```

`--scope user` makes Kinesis available in every project. Without it, Claude Code saves the connection for the current directory. The URL is quoted so shells handle its query string correctly.
{% endstep %}

{% step %}

### Sign in

Start Claude Code and run `/mcp`. Select **kinesis**, then **Authenticate**. In the browser, sign in to Kinesis, review the permissions and choose the organizations the connection can reach. Approve, then return to Claude Code.

If an organization requires SSO, complete its SSO sign-in when prompted.
{% endstep %}

{% step %}

### Check the connection

Confirm Kinesis is connected in `/mcp`, then send:

```
Use Kinesis to show my identity and list the organizations I can access.
Then ask which organization to use and list its projects. Do not change anything.
```

This setup exposes individual actions such as `whoami` and `list_orgs`. A successful check returns your Kinesis identity and the organizations available to the connection.
{% endstep %}
{% endstepper %}

## API key for CI or non-interactive use

For CI or `claude -p` without an interactive browser, create a scoped key in [Account settings → API keys](https://portal.kinesis.network/dashboard/account). Set `KINESIS_API_KEY` through your environment or CI secret store, then use the command for your shell:

{% tabs %}
{% tab title="macOS / Linux / WSL" %}

```bash
claude mcp add --transport http --scope user kinesis "https://mcp.kinesis.network/mcp" --header "Authorization: Bearer $KINESIS_API_KEY"
```

{% endtab %}

{% tab title="PowerShell" %}

```powershell
claude mcp add --transport http --scope user kinesis "https://mcp.kinesis.network/mcp" --header "Authorization: Bearer $env:KINESIS_API_KEY"
```

{% endtab %}
{% endtabs %}

Keep `--header` **after the URL**. It accepts multiple values and can consume the server name and URL if placed before them.

{% hint style="warning" %}
Your shell expands the variable before Claude Code saves the configuration. **The API key is stored as plain text in `~/.claude.json`** for this user-scoped setup. Protect that file and exclude it from source control and shared artifacts. OAuth avoids putting an API key in this configuration.
{% endhint %}

The API-key example uses the default compact catalog. See [connection options](/mcp/connect.md#choose-a-catalog-mode) for individual actions, selected groups and read-only discovery. If `kinesis` already exists, update that entry rather than adding a second connection.

## If it does not connect

Run `claude mcp get kinesis` to inspect the saved server. Use `/mcp` to authenticate or reconnect after a change. For missing permissions, return to Kinesis authorization or update the key's scopes; changing the URL does not grant access.

[Shared troubleshooting](/mcp/connect.md#troubleshooting) · [Try a workflow](/mcp/workflows.md) · [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kinesis.network/mcp/connect/claude-code.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.