Connect Beacon to Code Editors
Configuration methods for connecting Beacon MCP to VS Code, JetBrains IDEs, Cursor, and other MCP-compatible editors.
Last updated: April 9, 2026
Most code editors with MCP support accept server configuration in one of two formats: an HTTP URL or a JSON configuration block. Beacon supports HTTP connections.
Server URL
If your editor has an “Add MCP server” dialog that accepts a URL directly, use:
https://beacon.sirenaffiliates.com/beacon/v1/mcp
HTTP JSON configuration
If your editor expects a JSON configuration block (common in settings files), use:
{
"beacon": {
"type": "url",
"url": "https://beacon.sirenaffiliates.com/beacon/v1/mcp"
}
}
Where this JSON goes depends on the editor. Some use a dedicated MCP settings panel, others expect it in a project or user settings file.
Editor-specific documentation
Each editor handles MCP configuration differently. Refer to the vendor documentation for where to add the configuration:
- VS Code (Claude Code extension): Claude Code documentation
- JetBrains IDEs (AI Assistant plugin): Settings > Tools > AI Assistant > Model Context Protocol
- Cursor: Cursor MCP documentation
The configuration above works with any editor that supports MCP over HTTP.