---
title: "MySpec in your IDE"
description: "Browse spec files, comment and update tasks from VS Code or a JetBrains IDE, signed in with your MySpec account."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.myspec.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MySpec in your IDE

The MySpec extensions bring a project's spec files, tasks and discussions into
your editor, next to the code you build from them. There is one for
**VS Code** (and editors built on it) and one for **JetBrains IDEs**. Both work
the same way and share one sign-in.

## What you can do

- **Browse** a project's spec files as a folder tree, open them read-only
  (Markdown preview works) and step through their last 10 revisions. Compare a
  revision with the current version or the one before it.
- **Discuss**: see comment threads in the editor gutter, start a thread on the
  text you select, reply, resolve or reopen, and edit or delete your own
  comments.
- **Plan**: see the project's tasks, yours by default, and change their status,
  assignee, priority, story points, cycle, dates and labels. Changes are staged
  on your machine, like a shopping cart, and sent to MySpec together when you
  **Submit**.
- **Download** a spec file, a revision, an attachment or a whole folder.
- **Copy a prompt for your AI agent**: save the spec files behind a set of
  tasks under `.specs/` in your workspace and copy a prompt that lists the
  tasks in full. Paste it into any coding agent; it needs no MySpec access.
- **Open in MySpec** from anything to continue in the [MySpec app](https://app.myspec.dev).

Spec files are read-only in the IDE. Changing them, running sessions and
managing projects happens in the MySpec app, or through the
[MCP servers](https://docs.myspec.dev/mcp/).

## Supported editors

| Extension | Works in | Get it from |
|---|---|---|
| [MySpec for VS Code](https://docs.myspec.dev/ide/vscode/) | VS Code 1.95 or later | [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=myspec.myspec-vscode) |
| | Cursor, Windsurf, VSCodium and other VS Code-based editors | [Open VSX](https://open-vsx.org/extension/myspec/myspec-vscode) |
| [MySpec for JetBrains IDEs](https://docs.myspec.dev/ide/jetbrains/) | IntelliJ IDEA, PyCharm, WebStorm, GoLand and every other IntelliJ-based IDE, version 2025.3 or later | [JetBrains Marketplace](https://plugins.jetbrains.com/plugin/35781-myspec) |

Both are free. You need a MySpec account and to be a member of at least one
organization. If you do not have one yet, follow the
[Quickstart](https://docs.myspec.dev/get-started/quickstart/).

## How sign-in works

A browser sign-in is made once per machine, and the local MCP server and both
IDEs share it. There are two ways to sign in:

| | Browser sign-in | API token |
|---|---|---|
| How | Sign in to MySpec in your browser and approve the request | Paste an [API token](https://docs.myspec.dev/mcp/api-tokens/) (`msp_pat_…`) |
| Organization | Pick one when you sign in; switch any time | Fixed to the token's organization |
| Access | Everything your [project role](https://docs.myspec.dev/guides/teams-and-project-access/) allows | **Read only** or **Read and write**, as chosen when you created the token |
| Shared with | The [local MCP server](https://docs.myspec.dev/mcp/local-server/), VS Code and JetBrains IDEs on this machine | Only the IDE you entered it in |
| Best for | Your own laptop or desktop | A shared machine, or when you want read-only access |

Use the browser sign-in unless you have a reason not to.

### One sign-in for every MySpec tool

The browser sign-in is saved in `~/.myspec/` in your home folder, the same
place `npx @myspec/mcp-server login` saves it. So:

- If you already signed in with the local MCP server, the IDE is signed in too.
  There is nothing to do.
- Signing in, switching organization or signing out in one tool does the same
  in the others.

An API token entered in the IDE is different: it is kept in the IDE's own
secret storage (VS Code's secret storage, or the JetBrains password safe) and
used only by that IDE. It never changes what the MCP server signs in as.

### Which credential the IDE uses

When more than one is available, the IDE uses the first of these, and only
that one:

1. An API token you entered in the IDE.
2. The `MYSPEC_API_TOKEN` environment variable, if the IDE was started with it.
3. An API token saved in `~/.myspec/oauth_creds.json`.
4. The browser sign-in saved in `~/.myspec/`.

The account menu shows which one is in use. Signing out removes a browser
sign-in, but keeps an API token saved in `~/.myspec/oauth_creds.json`; delete
its `apiToken` field to stop using it.

### Organizations

Every sign-in works in one organization at a time. With a browser sign-in,
you pick it when you sign in (if you belong to more than one) and can switch
later with **Switch organization**. An API token always works in the
organization it was created for; to use another, create a token for it.

### Read-only tokens

A **Read only** API token can browse and download. Commenting and task changes
are turned off, and the account menu shows **Read-only token**.

## Link a project

After you sign in, you link a MySpec project to the folder (VS Code) or project
(JetBrains) you have open. The IDE remembers the link, so the right MySpec
project is there each time you reopen that folder. Different folders can link
different projects.

## Get started

- [VS Code](https://docs.myspec.dev/ide/vscode/) — Install the extension in VS Code, Cursor, Windsurf or VSCodium and sign in.
- [JetBrains IDEs](https://docs.myspec.dev/ide/jetbrains/) — Install the plugin in IntelliJ IDEA, PyCharm, WebStorm, GoLand and more, and sign in.

Source: https://docs.myspec.dev/ide/index.mdx
