How to Use the FOSSA (License Compliance) MCP in Cursor

Q: How do I add the FOSSA (License Compliance) MCP Server to Cursor?

Add the server configuration to your global /.cursor/mcp.json or your project-specific .cursor/mcp.json file. Once saved, enable Agent mode in the Cursor chat panel to grant the editor access to the compliance tools.

Q: Can Cursor automatically fix licenses flagged by FOSSA (License Compliance)?

Yes, when Cursor detects a violation using getrevisiondependencies, you can instruct the AI agent to rewrite your package manifest. The editor will replace the restricted package with an approved alternative that fits your legal requirements.

Q: How do I inspect a specific build version?

You can ask Cursor to run getrevision for any target commit hash or build tag. The editor pulls the compliance details and lists any license issues directly in your chat sidebar.

Track license compliance and security vulnerabilities in Cursor as you write code with this FOSSA MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect FOSSA (License Compliance) MCP to Cursor

Create your Vinkius account to connect FOSSA (License Compliance) to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup FOSSA (License Compliance) with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Inline Vulnerability Scans in Cursor

The `check_vulnerabilities` tool fetches real-time security alerts for your active dependencies directly inside your editing session. Cursor uses this data in Agent mode to highlight vulnerable packages in your package files before you run a local build. This means you can ask the editor to automatically write a pull request updating the affected dependency. You bypass the feedback loop of waiting for a CI failure.

Map Project Dependencies in the Editor

The `get_revision_dependencies` tool retrieves the exact dependency graph of your current project revision directly into Cursor. The editor uses this structural data to let you inspect deep-nested licenses while writing code. If you need to know where a package came from, Cursor calls `get_parent_projects` to trace its lineage. You can verify if a copyleft license is bleeding into your proprietary codebases without leaving your terminal.

Retrieve FOSSA Project Revisions via Cursor

The `list_projects` and `list_revisions` tools let you browse your organization's remote FOSSA inventory from the editor's sidebar using this MCP Server. Cursor queries these endpoints to match your local branch history with your remote compliance state. You can then run `get_revision` to check if your current commit has already been analyzed by your security team. This keeps your local development aligned with your organization's compliance targets.

Setup guide

Set up FOSSA (License Compliance) MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the FOSSA (License Compliance) MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent FOSSA (License Compliance) transactions." If the MCP tools are loaded correctly, Cursor will call the FOSSA (License Compliance) tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "fossa-license-compliance-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FOSSA. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect FOSSA (License Compliance) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about FOSSA (License Compliance) MCP in Cursor

Add the server configuration to your global `~/.cursor/mcp.json` or your project-specific `.cursor/mcp.json` file. Once saved, enable Agent mode in the Cursor chat panel to grant the editor access to the compliance tools.

Yes, when Cursor detects a violation using `get_revision_dependencies`, you can instruct the AI agent to rewrite your package manifest. The editor will replace the restricted package with an approved alternative that fits your legal requirements.

Yes, the MCP Server runs as a local background process managed by Cursor. It uses your local FOSSA API key to communicate with the compliance registry, keeping your dependency queries private.

You can ask Cursor to run `get_revision` for any target commit hash or build tag. The editor pulls the compliance details and lists any license issues directly in your chat sidebar.

The MCP Server only transmits package names, dependency locators, and revision hashes to the FOSSA API for verification. Your raw source code, proprietary logic, and local file paths never leave your local Cursor environment.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript