MCP Lite Wrappers

You can run lightweight MCP wrappers that consolidate multiple tools into single actions, dramatically reducing token usage while giving you a unified interface for common tasks across Supabase, Linear, Chrome DevTools, and Context7.

How to use

All actions pass through a single tool per service, using an action field and an optional payload. You interact with plain, structured actions like { action: "list_projects" } or { action: "execute_sql", payload: { query: "SELECT * FROM users" } }. Each service exposes a focused set of actions that map to their underlying APIs, while the wrapper handles the routing and formatting.

How to install

Prerequisites you need installed on your machine before setting up these MCP wrappers are Node.js and npm.

Install the desired wrapper package for your MCP server:

# Supabase wrapper
npm install supabase-lite-mcp

# Linear wrapper
npm install linear-lite-mcp

# Chrome wrapper
npm install chrome-lite-mcp

# Context7 wrapper
npm install context7-lite-mcp

Configuration and usage examples

Configure your MCP client to use each wrapper as a local (stdio) server. The examples below show how to wire up each wrapper in your MCP settings.

{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": ["supabase-lite-mcp"],
      "env": {
        "SUPABASE_ACCESS_TOKEN": "your-access-token",
        "SUPABASE_PROJECT_REF": "your-project-ref"
      }
    },
    "linear": {
      "command": "npx",
      "args": ["linear-lite-mcp"],
      "env": {
        "LINEAR_API_KEY": "lin_api_xxxxx"
      }
    },
    "chrome": {
      "command": "npx",
      "args": ["chrome-lite-mcp"],
      "env": {
        "CHROME_PATH": "/path/to/chrome",
        "CHROME_HEADLESS": "true"
      }
    },
    "context7": {
      "command": "npx",
      "args": ["context7-lite-mcp"],
      "env": {
        "CONTEXT7_API_KEY": "your-api-key"
      }
    }
  }
}

Security and best practices

Only expose the wrappers to trusted clients, and store API keys and tokens securely. Use environment variables to inject secrets at runtime, and restrict the scopes of tokens to the minimum required permissions.

Notes and troubleshooting

If an environment variable is optional, you can omit it. Ensure that the command and arguments exactly match the configuration shown above for each wrapper, so the MCP runtime can start the appropriate process.

Available tools

supabase-metadata

Unified access to Supabase tools consolidated under the single supabase tool (example: list_projects, execute_sql, deploy_edge_function)

linear-lite-actions

Unified Linear actions including issue management, comments, and user/teams/project queries (example: create_issue, search_issues, get_user_teams)

chrome-lite-actions

Unified Chrome automation actions including navigation, clicking, filling, extraction, and screenshots (example: navigate_page, click, extract, take_screenshot)

context7-lite-actions

Context7 library/docs tooling actions including resolve_library_id and get_library_docs