VibeFrame

https://github.com/taggartbg/vibeframe
Admin
VSCode Extension to enable UIs for MCP Servers (SSE)
Tokens:628
Snippets:6
Trust Score:7.7
Update:1 year ago
Show doc for...
Tokens:
Raw
### Install Vibeframe VS Code Extension via CLI

Source: https://github.com/taggartbg/vibeframe/blob/main/README.md

Command-line instruction to install the Vibeframe VSIX package into VS Code from a local file. This method is useful for offline installations or specific versions.

```Shell
code --install-extension vibeframe-0.1.0.vsix
```

--------------------------------

### Build Vibeframe VS Code Extension from Source

Source: https://github.com/taggartbg/vibeframe/blob/main/README.md

This section provides the complete set of commands required to clone the Vibeframe VS Code extension repository, install its dependencies, compile the source code, and package the extension for distribution. These steps are crucial for local development, contribution, and testing.

```bash
# Clone the repository
git clone https://github.com/your-org/vibeframe.git
cd vibeframe

# Install dependencies
npm install

# Build the extension
npm run compile

# Package the extension
npm run package
```

--------------------------------

### Configure MCP Server for Windsurf

Source: https://github.com/taggartbg/vibeframe/blob/main/README.md

JSON format for defining a single MCP server's URL and an optional name within Windsurf's configuration file (e.g., `mcp_config.json`). This format is simpler, focusing on a primary server connection.

```JSON
{
  "url": "https://example-mcp-server.com",
  "name": "Optional Server Name"
}
```

--------------------------------

### Configure MCP Servers for Cursor and VS Code

Source: https://github.com/taggartbg/vibeframe/blob/main/README.md

JSON format for defining multiple MCP server URLs, names, and types within Cursor's or VS Code's configuration files (e.g., `mcp.json`). It supports both simple URL strings and detailed objects with additional metadata.

```JSON
{
  "mcpServers": {
    "server1": "https://example-mcp-server.com",
    "server2": {
      "url": "https://another-mcp-server.com",
      "name": "My Custom Server Name",
      "type": "sse"
    }
  }
}
```

--------------------------------

### Manually Configure MCP Servers in VS Code Settings

Source: https://github.com/taggartbg/vibeframe/blob/main/README.md

JSON array format for adding custom MCP server URLs and names directly into VS Code's `settings.json` under the `vibeframe.manualServerUrls` setting. This allows users to define servers not automatically discovered.

```JSON
"vibeframe.manualServerUrls": [
  {
    "name": "My MCP Server",
    "url": "https://my-mcp-server.example.com"
  }
]
```

--------------------------------

### Configure MCP Servers for VS Code Workspace

Source: https://github.com/taggartbg/vibeframe/blob/main/README.md

JSON format for defining MCP server URLs, names, and types specifically within a VS Code workspace configuration file (e.g., `.vscode/mcp.json`). This configuration takes precedence over global settings for the current workspace.

```JSON
{
  "servers": {
    "server1": "https://example-mcp-server.com",
    "server2": {
      "url": "https://another-mcp-server.com",
      "name": "My Custom Server Name",
      "type": "sse"
    }
  }
}
```
Tokens:
Raw