Skip to main content
This guide shows you how to configure the Sita MCP server in Cline, the powerful VSCode extension for AI-assisted coding.
You must configure the MCP server for each repository you want to work with. Each repository requires its own configuration section with a unique repo ID.

​
Configuration Steps

1

Open MCP Settings

In VSCode with Cline installed, look at the top right corner of the Cline interface. You’ll see the MCP icon - it looks like 3 stacked layers. Click on this icon to open the MCP servers panel.
2

Access Installed Servers

Once the MCP panel opens, click on the “Installed” tab. This shows all currently configured MCP servers.
3

Configure MCP Servers

Click the “Configure MCP Servers” button. This opens the cline_mcp_settings.json file in your editor where you can add the Sita configuration.
4

Add Configuration

Add the appropriate configuration based on whether you’re setting up one repository or multiple repositories (see examples below).
5

Save and Reload

Save the configuration file. The MCP server will automatically reload with your new settings.

​
Single Repository Configuration

To configure Sita for a single repository, add this to your cline_mcp_settings.json: 
{
  "mcpServers": {
    "code-qna": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:3000/api/mcp",
        "--header",
        "x-repo-id: YOUR_REPO_ID"
      ]
    }
  }
}
Replace YOUR_REPO_ID with your repository ID. The repo id can be copied from repos tab.

​
Multiple Repository Configuration

To configure multiple repositories, add separate server entries for each: 
{
  "mcpServers": {
    "frontend-qna": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:3000/api/mcp",
        "--header",
        "x-repo-id: frontend-app"
      ]
    },
    "backend-qna": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:3000/api/mcp",
        "--header",
        "x-repo-id: backend-api"
      ]
    },
    "mobile-qna": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:3000/api/mcp",
        "--header",
        "x-repo-id: mobile-app"
      ]
    }
  }
}
Give each server configuration a descriptive name (like frontend-qna, backend-qna) to easily identify which repository it connects to.

​
Verification

After adding the configuration and saving the file, you should see:
  • Your server name(s) appear in the MCP panel’s “Installed” tab
  • A green indicator showing the server is connected
  • The codebase-qna tool available when using Cline

​
Next Steps