Skip to main content
Glama

MCP Suite Manager (Model Context Protocol) - SEOSiri

πŸ“– Official Architecture & Usability Guide: SEOSiri Technical Guide | Developer Portal & Live Topology | Central Master Directory | Marketplace Listing

SEOSiri MCP Suite Manager is an enterprise Model Context Protocol (MCP) orchestrator for Visual Studio Code, Cursor IDE, Claude Desktop, and Cline. It eliminates manual JSON-RPC syntax errors, auto-generates client configuration files, audits extension security manifests, and monitors live Cloudflare Edge Gateways (*.seosiri.com) directly from your editor.


πŸ› οΈ In-Editor Usability & Operational Manual

Step 1: Install the Extension

  • From VS Code / Cursor Marketplace:

    1. Open your editor and press Ctrl + Shift + X (or Cmd + Shift + X on macOS).

    2. Search for SEOSiri MCP or seosiri-vscode-mcp-manager.

    3. Click Install.

  • Via Command Line (VSIX Install):

    code --install-extension seosiri-vscode-mcp-manager-1.0.1.vsix

Step 2: Open the Command Palette

Press Ctrl + Shift + P (or Cmd + Shift + P on macOS) to access all SEOSiri MCP operations:

> SEOSiri: Generate MCP Client Configuration (Cursor / Claude / VS Code)
> SEOSiri: Audit Extension Manifest (Security & Permissions Scan)
> SEOSiri: Inspect Live Gateways (Telemetry & Latency Traces)
> SEOSiri: Sync Workspace Settings & Linters

Step 3: Auto-Generate MCP Client Configurations

Select SEOSiri: Generate MCP Client Configuration and choose your target AI environment:

1. For Cursor IDE (.cursor/mcp.json):

The extension automatically writes the verified JSON-RPC tool configuration to your project:

{
  "mcpServers": {
    "seosiri-biopharma": {
      "command": "npx",
      "args": ["-y", "@seosiri/biopharma-mcp"]
    },
    "seosiri-aeo-geo": {
      "command": "uvx",
      "args": ["seosiri-aeo-geo-mcp"]
    },
    "seosiri-industrial-ai": {
      "command": "npx",
      "args": ["-y", "@seosiri/industrial-ai-gateway"]
    }
  }
}

2. For Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "vscode-mcp-manager": {
      "command": "node",
      "args": ["D:/seosiri-vscode-mcp-manager/dist/index.js"]
    }
  }
}

Step 4: Audit Extension Manifest Security (package.json)

Run SEOSiri: Audit Extension Manifest against any extension in your workspace:

  • Validates activationEvents and engines.vscode compatibility.

  • Scans for un-sandboxed command execution risks.

  • Redacts hardcoded API tokens, private keys, and internal network endpoints.


Step 5: Live Cloudflare Edge Telemetry Inspection

Run SEOSiri: Inspect Live Gateways to query live sub-10ms response latencies and server health across all 13 Cloudflare edge gateways:

  • biopharma.seosiri.com (4PL Curves & FDA 21 CFR Part 11)

  • iaig.seosiri.com (Industrial AI & ROS 2 Robotics)

  • rovomcp.seosiri.com (Atlassian Rovo & PII Shield)

  • aeo.seosiri.com (AEO/GEO Intelligence & /llm.txt)

  • schema.seosiri.com (Schema.org JSON-LD & GA4)

  • keywords.seosiri.com (384-D Vector RAG & Intent)

  • vscode.seosiri.com (VS Code Suite Gateway)


Related MCP server: Code MCP Server

πŸš€ 4 Autonomous MCP Tools Exposed to AI Agents

Tool Identifier

Capability & Primary Function

Target Protocol

vscode_generate_mcp_config

Compiles verified JSON-RPC client configurations for zero-setup execution.

Stdio / JSON-RPC 2.0

vscode_audit_extension_manifest

Scans package.json for security vulnerabilities, activation triggers, and leaks.

Static AST Analysis

vscode_sync_workspace_settings

Synchronizes team linter rules, TypeScript settings, and MCP permissions.

Workspace Sync

vscode_inspect_live_gateways

Queries real-time HTTP latency and active tool capacity across all 13 gateways.

Edge Telemetry


πŸ”’ Zero-Trust Privacy & Security Guarantee

SEOSiri operates on a strict local-first, zero-log execution plane. All configuration generation, manifest audits, and workspace synchronizations run in-memory within your local workstation without third-party tracking.


πŸ‘¨β€πŸ’» Lead Architect & Support

Designed and engineered by Momenul Ahmad, Founder of SEOSiri Enterprise Labs.


πŸ“„ License

Distributed under the MIT License.

Available Tools

4 tools
vscode_audit_extension_manifestA

Audits VS Code extension package.json manifests against Microsoft Marketplace and security standards. Checks for required engines, activationEvents, publisher IDs, category validity, and unsafe dependencies. Use before packaging .vsix extension binaries.

Inputs: manifest_json (required).

vscode_generate_mcp_configA

Generates ready-to-use, verified MCP client configuration files for Claude Desktop, Cursor IDE, Roo Code / Cline, and OpenAI Responses API. Automatically maps local stdio commands (npx/uvx) and remote Cloudflare SSE edge streams. Use when configuring an AI agent or IDE to communicate with SEOSiri servers. Do not use for non-MCP IDE settings.

Inputs: client_type (required), active_servers.

vscode_inspect_live_gatewaysA

Queries real-time operational status, sub-millisecond response latency, and supported protocol transports across all 13 official SEOSiri Cloudflare edge gateways (*.seosiri.com). Use to verify network connectivity before invoking remote MCP tools.

Inputs: filter_protocol.

vscode_sync_workspace_settingsA

Generates standardized enterprise workspace settings (.vscode/settings.json) and recommended extensions (.vscode/extensions.json) for TypeScript, ESLint, Tailwind CSS, and MCP development. Use to establish consistent team settings across VS Code and Cursor.

Inputs: target_ide (required), enforce_strict_formatting.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct artifact or action: generating MCP client configs, auditing extension manifests, syncing workspace settings, and inspecting live gateways. Even the two config-producing tools are clearly separated by output type and intended usage.

    Naming Consistency5/5

    All tool names follow the same vscode_<verb>_<object> pattern, using specific verbs and clear nouns. There are no mixed conventions or vague actions.

    Tool Count5/5

    Four tools form a compact, purposeful set well within the ideal range. Each tool covers a separate facet of the VS Code/MCP configuration workflow without redundancy.

    Completeness4/5

    The set covers configuration generation, workspace standardization, extension validation, and gateway health verification, which supports a solid setup workflow. Minor gaps existβ€”such as no explicit existing-config validation or server removalβ€”but these do not create dead ends for the apparent purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers