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.

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

1. Locate Tabnine Configuration

Tabnine stores its MCP configuration in the following location.

.tabnine/mcp_servers.json

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

2. Configure the MCP Server

Edit mcp_servers.json and add the Mobb MCP configuration:

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

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.

4. Reload Tabnine

Reload VS Code to apply the new configuration:

> Developer: Reload Window

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

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 project"

• “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:

- 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: