Quick Start

Quick Start Guide: Using SigilAI Cloud MCP Server

This guide helps you quickly connect your AI development tools and assistants to the SigilAI cloud-hosted Model Context Protocol (MCP) server. SigilAI provides a managed MCP service, allowing you to easily integrate powerful security scanning into your workflows.

Prerequisites

Before you begin, ensure you have:

  1. API Key: Obtain your API key from the SigilAI Telegram bot at https://t.me/SigilAIBot. This key is essential for authenticating with the MCP server.

  1. MCP Server Endpoint: The SigilAI MCP Server URL is https://mcp.sigilai.io/sse .

  2. Compatible AI Client: An AI assistant or development tool that supports MCP integration, such as Cline, Cursor, or Claude Desktop.

Connecting Your AI Client to SigilAI MCP Server

The SigilAI MCP server allows various AI clients to access its security tools. Below are configuration examples for popular clients. The general principle involves adding SigilAI as an MCP server provider within your client's settings, using your API key and the server endpoint.

To configure SigilAI MCP server access within Cline:

  1. Access MCP Settings:

    • You (as the user interacting with Cline) would typically inform Cline: "Please add a new MCP server configuration."

    • Cline would then guide you or use its internal capabilities to update its MCP server list.

  2. Provide SigilAI MCP Server Details: When prompted by Cline, or by editing Cline's MCP configuration file (if accessible to you as a user/developer of Cline), provide the following:

    • Server Name: SigilAI (or any preferred display name)

    • Server URL / Endpoint: https://mcp.sigilai.io/sse (or your specific endpoint)

    • Authentication Method: Bearer Token

    • API Key / Token: Your SigilAI API Key

    • (Optional) Instructions/Description: You can copy the server instructions from the SigilAI MCP server if your client supports displaying them.

  3. Save and Activate:

    • Confirm the settings. Cline should then be able to connect to the SigilAI MCP server and list its available tools (e.g., scan_url, scan_file).

  4. Usage Example with Cline:

    User: Cline, please scan the URL https://example-suspicious.com using SigilAI.
    
    Cline: (Internally makes an MCP tool_call to SigilAI's scan_url tool)
           Okay, I've scanned https://example-suspicious.com using SigilAI. 
           The result indicates it is potentially malicious due to [reason]. 
           It's advisable not to visit this site.

Verifying the Connection

Once configured, your AI client should ideally indicate a successful connection or list the tools available from the SigilAI MCP server (e.g., scan_url, scan_file).

You can perform a simple test by asking your AI client to use one of SigilAI's tools:

  • Ask to scan a known safe URL: "Please scan the URL https://www.google.com using SigilAI." The expected response should indicate the URL is safe.

  • Ask to scan a (non-malicious) test file content (if applicable to your client): "Please scan this JavaScript code for issues using SigilAI: function greet() { console.log('Hello'); }" The expected response should indicate no critical vulnerabilities.

Next Steps

With your AI client successfully connected to the SigilAI Cloud MCP Server, you can now:

  • Integrate into Workflows: Start using SigilAI's security scanning tools within your AI-assisted development, research, or content analysis tasks.

  • Review API Reference: For more technical details on tool invocation, see the API Reference.

If you encounter issues, consult the FAQ & Troubleshooting page or contact SigilAI support.

Last updated