Search for a command to run...
As a former Paratrooper Medic and Mass Casualty Coordinator, I made the leap into software engineering. Through my journey, I've continued to grow and learn, and I'm eager to share my knowledge with others. As a self-taught software engineer, I'm passionate about empowering others to pursue their dreams and learn new skills.
A Comprehensive Technical Guide
Weighing Performance vs Build Time
This tutorial walks through the process of using the ArDrive Turbo CLI to top up your account with ARIO tokens. It's an extremely simple process and makes it very easy to manage your Turbo Credit balance without ever leaving your terminal or your IDE...
Plan DevRel Strategies the Army Ranger Way
I Had a hell of a time getting my Supabase MCP Server working. I figured that, because I went through the ringer on figuring out how to fix it, that I would share with you all that are probably googling how to get it fixed a guide to do just that.
If you're unaware, the current official MCP server for Supabase seems to not be working very well at the moment: https://github.com/supabase-community/supabase-mcp/issues/28
This guide walks through setting up the Supabase Model Context Protocol (MCP) server with Cursor, allowing you to interact with your Supabase database directly through Cursor's AI assistant.
sbp_)The Supabase MCP server requires specific packages to work properly. Install them locally in a dedicated directory:
# Create a directory for MCP packages
mkdir -p ~/.cursor/mcp-packages
# Navigate to the directory
cd ~/.cursor/mcp-packages
# Initialize a package.json
npm init -y
# Install required packages
npm install @supabase/mcp-server-supabase @modelcontextprotocol/sdk
# Create a directory for MCP packages
mkdir -p %APPDATA%\Cursor\mcp-packages
# Navigate to the directory
cd %APPDATA%\Cursor\mcp-packages
# Initialize a package.json
npm init -y
# Install required packages
npm install @supabase/mcp-server-supabase @modelcontextprotocol/sdk
mkdir -p ~/.cursor
touch ~/.cursor/mcp.json
{
"mcpServers": {
"supabase": {
"command": "node",
"args": [
"/Users/YOUR_USERNAME/.cursor/mcp-packages/node_modules/@supabase/mcp-server-supabase/dist/stdio.js",
"--access-token",
"YOUR_SUPABASE_PAT_HERE"
]
}
}
}
YOUR_USERNAME with your Mac usernameYOUR_SUPABASE_PAT_HERE with your Supabase Personal Access TokenCreate or edit your Cursor MCP configuration file at %APPDATA%\Cursor\mcp.json
Add the Supabase MCP server configuration:
{
"mcpServers": {
"supabase": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@supabase/mcp-server-supabase",
"--access-token",
"YOUR_SUPABASE_PAT_HERE"
]
}
}
}
Note: We're intentionally omitting @latest to avoid potential dependency conflicts.
{
"mcpServers": {
"supabase": {
"command": "cmd",
"args": [
"/c",
"node",
"%APPDATA%\\Cursor\\mcp-packages\\node_modules\\@supabase\\mcp-server-supabase\\dist\\stdio.js",
"--access-token",
"YOUR_SUPABASE_PAT_HERE"
]
}
}
}
YOUR_SUPABASE_PAT_HERE with your Supabase Personal Access Tokenls -la ~/.cursor/mcp-packages/node_modules/@supabase/mcp-server-supabase/dist/
stdio.js exists in this directory and is executable.dir %APPDATA%\Cursor\mcp-packages\node_modules\@supabase\mcp-server-supabase\dist\
stdio.js exists in this directory.The setup described above runs the MCP server directly on your system, which has some security implications:
Using Docker provides better isolation and security. Here's how to set it up:
Create a file named Dockerfile in a directory of your choice:
FROM node:18-slim
RUN npm install -g @supabase/mcp-server-supabase @modelcontextprotocol/sdk
ENTRYPOINT ["supabase-mcp", "--access-token"]
CMD ["YOUR_SUPABASE_PAT_HERE"]
Replace YOUR_SUPABASE_PAT_HERE with your Supabase PAT.
docker build -t supabase-mcp .
{
"mcpServers": {
"supabase": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"supabase-mcp"
]
}
}
}
{
"mcpServers": {
"supabase": {
"command": "cmd",
"args": [
"/c",
"docker",
"run",
"-i",
"--rm",
"supabase-mcp"
]
}
}
}
Regardless of which approach you choose:
If you see an error message like:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '@modelcontextprotocol/sdk/dist/esm/server/stdio.js'
Try the following solutions (in order of simplicity):
Remove @latest from npx command:
@latest suffix, remove it:{
"mcpServers": {
"supabase": {
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase",
"--access-token",
"YOUR_SUPABASE_PAT_HERE"
]
}
}
}
Use a direct local installation:
Try global installation:
npm install -g @supabase/mcp-server-supabase @modelcontextprotocol/sdk
For Windows users:
mcp.json (no trailing commas, proper nesting)stdio.js, not cli.js)\\) in the JSON configurationOnce configured, you can interact with your Supabase database through Cursor's AI assistant:
Example prompts: