> For the complete documentation index, see [llms.txt](https://docs.mobb.ai/mobb-user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobb.ai/mobb-user-docs/getting-started/mobb-vibe-shield-mvs/tabnine-enterprise.md).

# VS Code + Tabnine Enterprise

## Prerequisites

Before setting up MVS, ensure the following:

* **Node.js v18.20 or later** is installed. (Check with `node --version`)
* **Tabnine Enterprise** plugin is installed and running inside VS Code.
* **Agent** mode is enabled. If you don't see the Agent mode, contact your Tabnine representative.

<figure><img src="/files/S1ltMG8m4axmHHRmM0Ng" alt="Here is an example showing Agent Mode available in the Tabnine plugin" width="375"><figcaption><p>Here is an example showing <strong>Agent Mode</strong> available in the Tabnine plugin</p></figcaption></figure>

***

## Modes Supported

Mobb Vibe Shield supports three primary modes in Tabnine Enterprise:

1. **scan\_and\_fix\_vulnerabilities**: Scans and fixes vulnerabilities in recently modified files.
2. **fetch\_available\_fixes**: Applies fixes from the Mobb platform if a matching fix report exists.
3. **check\_for\_new\_available\_fixes**: Triggers a background scan for new available fixes. The first call starts the scan, and MVS will continue to scan every 15 minutes.

***

## MVS Setup Instructions

### Step 1. Locate Tabnine Configuration

Tabnine stores its MCP configuration in the following location.

```
.tabnine/mcp_servers.json
```

<figure><img src="/files/YoXE1SHerzUclqRTH46A" alt=""><figcaption></figcaption></figure>

If you don't see the `mcp_servers.json` file, you can create a new one.

***

### Step 2. Configure the MCP Server

Edit `mcp_servers.json` and add the Mobb MCP configuration:

```json
{
  "mcpServers": {
    "mobb-mcp": {
      "command": "npx",
      "args": ["--yes", "mobbdev@latest", "mcp"]
    }
  }
}
```

<figure><img src="/files/cnsLWrSI0TzVJBF66wdd" alt=""><figcaption></figcaption></figure>

#### Single-Tenant Configuration (Optional)

For enterprise customers using a single-tenant Mobb instance, add the following environment variables in your Tabnine configuration:

```
API_URL=https://api-st-<YOUR_TENANT_NAME>.mobb.ai/v1/graphql
WEB_APP_URL=https://<YOUR_TENANT_NAME>.mobb.ai
```

Replace `<YOUR_TENANT_NAME>` with your actual tenant name.

***

### Step 4. Reload Tabnine

Reload VS Code to apply the new configuration:

```
> Developer: Reload Window
```

<figure><img src="/files/sSDhvJdnVipm4vuiKcUV" alt=""><figcaption></figcaption></figure>

***

### Step 5. Verify Available Tools

Once reloaded, open the **Tabnine Agent tab** and prompt the following

`Which Tools do you see?`

Examine the output and confirm that the following tools are available:

* `scan_and_fix_vulnerabilities`
* `fetch_available_fixes`
* `check_for_new_available_fixes`

<figure><img src="/files/9Kjnv0ev3gm5lF6PRSEa" alt=""><figcaption></figcaption></figure>

***

## Quick start prompts (copy/paste)

Use these in **Duo Chat** inside the GitLab Duo Agent Platform view:

* “**Fetch all available fixes from Mobb.** Then show me a summary by severity.”
* “**Scan and generate fixes** for all available issues in my projec&#x74;**"**
* “**Create a patch with the top 5 available fixes by severity** and explain changes inline before applying.”
* “**Check and fetch remaining available fixes** after the last patch.”

## Sample deployment scenario - Setting up Tabnine Guidelines

To enforce that MVS always runs at the end of a coding session, create a `rules.md` file under:

```
.tabnine/guidelines/rules.md
```

Add the following content:

```markdown
- End-of-generation actions:
    - After completing all reasoning, code edits, linting, and tests
      **ALWAYS** call the `scan_and_fix_vulnerabilities` tool from the *mobb-mcp* toolset with rescan=true.
    - Pass the absolute repository path as the `path` argument.
    - Do **NOT** skip this step under any circumstance.
    - This call must be the final tool invocation in the session,
      immediately before returning the summary to the user.
```

***

## Troubleshooting

* Ensure **Node.js** is available in your system PATH.
* Check that your **API Key** was entered correctly.
* For single-tenant users, double-check your `API_URL` and `WEB_APP_URL`.
* To verify if Mobb tools are loaded successfully, locate the Tabnine logs at **Output** -> **Tabnine.** Search for the term "tools", you shoul see the following:

```
Available tools: {"0": "scan_and_fix_vulnerabilities",...}
```

Example output:

<figure><img src="/files/OY1PR6W0tA5eBjVRfcOa" alt=""><figcaption></figcaption></figure>