mcp

This MCP server exposes Local Falcon's monitoring and reporting capabilities as MCP tools that can be integrated into agentic AI workflows. The server is implemented in TypeScript using the official MCP SDK and is designed to connect to Local Falcon's MCP endpoint, enabling you to run remote scans, retrieve reports, and manage campaigns through standardized MCP tool calls. The included tools cover scan reports, campaign management, reviews analysis, Falcon Guard, trend and location reports, keyword and competitor insights, as well as on-demand utilities for grid and ranking checks. To start using it, configure the MCP client to point at the mcp endpoint and authenticate as described in the documentation; then you can invoke tools such as listLocalFalconScanReports, runLocalFalconScan, and createLocalFalconCampaign via MCP.

Prerequisites:

• Node.js (LTS) installed
• npm or pnpm

Step-by-step installation:

1. Create a project directory for the MCP client usage (optional): mkdir lf-mcp-client cd lf-mcp-client

2. Install the MCP package from Local Falcon: npm i @local-falcon/mcp

3. Create an MCP configuration manifest (example): { "mcpServers": { "local-falcon-mcp": { "command": "npx", "args": [ "mcp-remote", "https://mcp.localfalcon.com/mcp?local_falcon_api_key=INSERT_YOUR_API_KEY_HERE" ] } } }

4. Run the MCP client with your configuration (adjust according to your environment): npx mcp-remote https://mcp.localfalcon.com/mcp?local_falcon_api_key=INSERT_YOUR_API_KEY_HERE

5. If you prefer STDIO-based setup, follow the README guidance and use the node-based index.js path provided by the installed package. For example, on macOS/Unix, you can launch using the node command and pointing to the installed dist/index.js with the appropriate LOCAL_FALCON_API_KEY in the environment.

Tips and notes:

• Authentication: Use OAuth where possible; otherwise, provide a Bearer Token or API key as shown in the Local Falcon documentation.
• If using the STDIO approach, you may need to supply LOCAL_FALCON_API_KEY via environment variables (e.g., LOCAL_FALCON_API_KEY) depending on your setup.
• The /sse endpoint is legacy; prefer the /mcp endpoint for new integrations.
• When deploying in CI or serverless environments, store API keys securely (e.g., secrets manager) and inject them at runtime.
• The MCP tools cover a wide range of capabilities (scans, campaigns, reports, location and keyword data, etc.). Use the provided tool names to build automation workflows and trigger actions programmatically.