> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/manage-spot/integrations/ai-assistants-mcp/connect-claude-code.md).

# Connect Claude Code

Connect Claude Code to your Spot with the MeltingSpot plugin, or by adding the MCP server from the command line.

There are two ways to connect Claude Code to your Spot:

* **with the MeltingSpot plugin (recommended)**: the connection is already set up, and instructions guide Claude Code to use MeltingSpot properly;
* **by adding the MCP server by hand**, with one command.

Before you start, check the [prerequisites](https://help.meltingspot.io/english/manage-spot/integrations/ai-assistants-mcp.md#before-you-start): you are an administrator of the Spot and the MCP server is enabled for this Spot.

## Install the MeltingSpot plugin (recommended)

1. In Claude Code, type:

   ```
   /plugin marketplace add meltingspot/meltingspot-for-ai
   /plugin install meltingspot@meltingspot
   ```
2. Type `/mcp` to sign in to MeltingSpot.
3. The MeltingSpot page opens in your browser: pick your Spot in **Spot to connect**, then click **Authorize**.

If you already installed the plugin on claude.ai, it is already available in Claude Code. To learn more about what it contains, see [MeltingSpot plugin and skills](https://help.meltingspot.io/english/manage-spot/integrations/ai-assistants-mcp/meltingspot-plugin-and-skills.md).

## Or: add the server by hand

1. In a terminal, add the server:

   ```bash
   claude mcp add --transport http --scope user meltingspot https://mcp.meltingspot.io/mcp
   ```

   The `--scope user` option makes MeltingSpot available in all your projects. Without it, it is only available in the current project.
2. Start Claude Code, then type:

   ```
   /mcp
   ```
3. Choose `meltingspot`, then **Authenticate**.
4. The MeltingSpot page opens in your browser: pick your Spot in **Spot to connect**, then click **Authorize**.

{% hint style="info" %}
If the browser does not open, copy the address shown by Claude Code and open it yourself.
{% endhint %}

## Use MeltingSpot

Make your request in Claude Code, for example: "List the invited members who have not joined my Spot yet."

## Reconnect

If the connection has expired, type `/mcp`, choose `meltingspot`, then **Re-authenticate**. You can also run:

```bash
claude mcp login meltingspot
```

## Disconnect MeltingSpot

* To sign out without removing the server: `/mcp`, `meltingspot`, then **Clear authentication**. Or:

  ```bash
  claude mcp logout meltingspot
  ```
* To remove a server added by hand, sign out first, then run:

  ```bash
  claude mcp remove meltingspot
  ```

{% hint style="info" %}
To work on another Spot, add a second server with the same address and another name, for example `meltingspot-academy`, then pick the other Spot on the MeltingSpot page.
{% endhint %}


---

# 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://help.meltingspot.io/english/manage-spot/integrations/ai-assistants-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.
