MCP For Claude Marketplace
Supabase Edge Function Deno Validator

Supabase Edge Function Deno Validator MCP Connector for Claude

A+

Detect Node.js incompatibilities in Supabase Edge Functions before deployment.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner
More Details Connect to Claude

Ensure your Supabase Edge Functions are ready for Deno Deploy. This MCP server provides deterministic validation of TypeScript code to prevent runtime failures caused by Node.js-specific patterns. Use validate_deno_imports to check for incompatible modules, audit_node_imports to identify risky imports like 'node:path', and check_env_access to ensure you are using Deno.env instead of process.env.

supabasedenoedge-functionsvalidationtypescriptdeployment

3 tools expose this connector's capabilities to your AI agent.

audit_node_imports

js specific modules that might not work in Deno environments. Audits Node.js imports in TypeScript code

check_env_access

env or Deno.env is being used. Checks for environment variable access in TypeScript code

validate_deno_imports

Validates if TypeScript code is compatible with Deno

See how to talk to your AI agent using Supabase Edge Function Deno Validator.

Is this code compatible with Supabase Edge Functions: 'import fs from "node:fs"; console.log(process.env.KEY);'

No, the code contains Node.js violations. It uses 'node:fs' and 'process.env', which are not supported in Deno.

Check if this function is safe for Deno: 'Deno.serve((req) => new Response("Hello"));'

Yes, the code uses Deno.serve and is compatible with the Deno runtime.

Audit this snippet for Node.js imports: 'import path from "node:path";'

The audit identified a violation: the use of 'node:path' is not compatible with Deno.

It scans your TypeScript code for Node.js-specific patterns that will fail in the Deno runtime used by Supabase Edge Functions.