> 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/cursor.md).

# Cursor

Connect Cursor to Kinesis manually, or add the local plugin with its deployment skill.

Connect Cursor's agent to Kinesis with a remote MCP server. For a guided repository deployment workflow, you can also install the Kinesis plugin locally while Marketplace approval is pending.

## Connect the server

{% stepper %}
{% step %}

### Add Kinesis

[**Add Kinesis to Cursor →**](https://cursor.com/en-US/install-mcp?name=kinesis\&config=eyJ1cmwiOiJodHRwczovL21jcC5raW5lc2lzLm5ldHdvcmsvbWNwIn0%3D)

Open the link on a computer with Cursor installed and review its install prompt. If the browser cannot open Cursor, use the file setup below.

Add this entry to **`~/.cursor/mcp.json`** for all projects, or **`.cursor/mcp.json`** in a project for just that project. On Windows, `~` means your user folder, typically `C:\Users\<you>`.

```json
{
  "mcpServers": {
    "kinesis": {
      "url": "https://mcp.kinesis.network/mcp"
    }
  }
}
```

If the file already contains servers, add `kinesis` inside the existing `mcpServers` object; keep the other entries. The URL loads the compact catalog, with separate read and write tools.
{% endstep %}

{% step %}

### Sign in

Open Cursor's **Customize** page and find **kinesis** in MCP servers. Enable it if needed and follow the connection's sign-in prompt. Sign in to Kinesis in the browser, review permissions and choose organizations, then approve and return to Cursor.

Complete organization SSO if prompted. If the new server is missing, run **Developer: Reload Window** from Cursor's command palette.
{% endstep %}

{% step %}

### Check the connection

Start an Agent chat and 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.
```

In compact mode, Cursor calls the `account` and `projects` tools with an action and its parameters. You can use natural language; you do not need to write the tool arguments yourself.
{% endstep %}
{% endstepper %}

## Add the deployment skill

The public [Kinesis Cursor plugin](https://github.com/kinesis-network/cursor-plugin) includes the MCP connection and **deploy-to-kinesis** skill. The skill checks your repository, Dockerfile, port and environment, follows the build and returns the deployed address.

While Marketplace approval is pending, install it as a local plugin:

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

```bash
git clone https://github.com/kinesis-network/cursor-plugin ~/.cursor/plugins/local/kinesis-network
```

{% endtab %}

{% tab title="PowerShell" %}

```powershell
git clone https://github.com/kinesis-network/cursor-plugin "$env:USERPROFILE/.cursor/plugins/local/kinesis-network"
```

{% endtab %}
{% endtabs %}

Run **Developer: Reload Window**, then open **Customize** and confirm the Kinesis plugin, MCP server and deployment skill are present. Authenticate its connection when prompted. If you already added the standalone server above, keep one Kinesis connection enabled to avoid duplicate tools.

Local plugin imports must be allowed by your organization. If policy blocks them, ask your Cursor administrator; the standalone MCP setup remains an option when permitted.

To use the skill, ask: **“Use deploy-to-kinesis to deploy this repository to Kinesis.”** Deployments use the selected organization's credits and your Kinesis permissions.

For later updates, open a terminal in that plugin folder and run `git pull --ff-only`, then reload Cursor. Do not clone over an existing folder.

[Connection options](/mcp/connect.md#choose-a-catalog-mode) · [Troubleshooting](/mcp/connect.md#troubleshooting) · [Cursor MCP documentation](https://cursor.com/docs/mcp) · [Local plugin documentation](https://cursor.com/docs/plugins#test-plugins-locally)


---

# 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/cursor.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.