Skip to main content

Integrations

Integrations​

LanOnasis exposes a Model Context Protocol (MCP) server plus REST, CLI, and SDK surfaces so AI agents, IDEs, and applications can connect to the memory and context platform.

This page covers the available integrations and how to connect each one.

Available integrations​

IntegrationSurfaceBest for
MCP serverSSE, WebSocket, HTTP REST, stdioAI agents, IDEs, and any MCP-compatible client
IDE integrationVSCode (desktop + web), Cursor, WindsurfEditors and AI coding assistants
Memory REST APIHTTP RESTServer-side applications and webhooks
Memory SDKTypeScript / PythonApplication code in your stack
CLITerminal / automationScripts, cron jobs, and local workflows
v-secure MCPMCP serverSecure secrets and resource access for AI tools

MCP integration​

The MCP server is the primary integration surface. It provides memory operations, API key management, memory intelligence, and behavior operations to any MCP-compatible client.

Production endpoint: https://mcp.lanonasis.com

Transports available:

  • SSE — https://mcp.lanonasis.com/sse
  • WebSocket — wss://mcp.lanonasis.com/ws
  • HTTP REST — https://mcp.lanonasis.com/api/v1/mcp/*
  • Stdio — local development and CLI integration

See the MCP Overview for the full tool reference, and the Production Server guide for deployment details.

Connection guides​

AI agents (Claude, Copilot, etc.)​

Connect an agent to the MCP server using your preferred MCP client configuration. Authenticate first via the Central Auth Gateway:

lanonasis auth login
lanonasis mcp connect
lanonasis mcp status

IDEs​

VSCode (desktop and web), Cursor, and Windsurf are supported. See the IDE Integration guide for per-editor configuration, including:

  • VSCode Memory Assistant extension configuration
  • Cursor MCP server setup
  • Windsurf mcpServers JSON configuration

Applications (REST API)​

Use the Memory REST API directly from any HTTP client:

curl -X POST https://api.lanonasis.com/v1/memories \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"title": "Example", "content": "Memory content", "memory_type": "context"}'

Your own codebase (SDKs)​

Pick the SDK for your language:

Scripts and automation (CLI)​

Use the CLI reference for terminal and automation workflows:

lanonasis memory create --inline
lanonasis memory search "project decisions" --type context --limit 10

Authentication​

All integrations require authentication. Two methods are supported:

  • OAuth 2.0 with PKCE — recommended for interactive applications and IDEs
  • Scoped API keys — recommended for automation and CI/CD

See the Central Auth Gateway guide and the Vendor Key Management page for key lifecycle details.