Updated
Cursor
Cursor reads MCP servers from .cursor/mcp.json in your project root. For a user-level global setup, place the file at ~/.cursor/mcp.json.
Native plugin listing pending
The Cursor Agent Plugin listing is still pending review and public readback. Use the direct MCP setup below until public listing and authenticated runtime acceptance are verified. The CLI installer does not provide a direct-MCP writer for this plugin route, so merge the entry manually. This guide does not claim plugin listing or authenticated Cursor runtime acceptance.
Authenticate local stdio
With Node.js 24 or newer, run npx -y lyrashield@0.2.14 login --oauth in the same OS account that runs Cursor. Select the intended workspace. The local MCP server reads the CLI credential store; no key belongs in the project config.
Configuration
Create or open .cursor/mcp.json in your project root and merge the following entry, preserving existing servers and settings.
Manual fallback: merge the following into .cursor/mcp.json. Recommended: run npx -y lyrashield@0.2.14 login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json. If you use an API key instead, set it in your private process environment before starting the client.
{
"mcpServers": {
"lyrashield": {
"command": "npx",
"args": [
"-y",
"@lyrashield/mcp@0.2.12"
],
"env": {
"LYRASHIELD_API_URL": "https://app.lyrashieldai.com"
}
}
}
}Important gotchas
- The project `.cursor/mcp.json` is shared by convention; never inline a literal API key into it.
.cursor/mcp.json inside your project root to share config with the team (each developer runs npx -y lyrashield@0.2.14 login --oauth locally). Place it at ~/.cursor/mcp.json for a personal global setup.Deeplink install
Cursor also documents a client-owned deeplink flow for registering MCP servers. See the Cursor MCP documentation for the current deeplink format.
Verify the connection
Reload the window and open Settings → MCP. The lyrashield server should appear with its tools. Then ask Cursor to call lyrashield_list_workspaces and confirm the intended workspace. Discovery and a successful authenticated read are separate checks; neither proves scan or write acceptance.
@lyrashield/mcp package is published on npm, so npx -y @lyrashield/mcp@0.2.12 resolves directly.