How do we configure workspace-specific plugin MCP servers

Support Help
,
1

I notice that I can create workspace-specific MCCP servers now, but is there a way to be able to use plugin MCP servers within a given workspace so that I could have different configurations for Supabase, for example, between different projects?

6

Plugin config variables are global right now - no per-workspace scoping. But you can get exactly what you want by adding the MCP server directly in each project’s .cursor/mcp.json instead of using the plugin.

For Supabase specifically, the hosted HTTP transport makes this clean. In each project’s .cursor/mcp.json:

{
"mcpServers": {
"supabase": {
"type": "http",
"url": "https://mcp.supabase.com/mcp?project_ref=YOUR_PROJECT_REF&read_only=true"
}
}
}

Swap YOUR_PROJECT_REF for each project. OAuth handles auth, and project_ref scopes the connection to that Supabase project.

For other plugin MCP servers where you need different env vars per project, same idea with envFile:

{
"mcpServers": {
"some-server": {
"command": "npx",
"args": ["-y", "some-mcp-package"],
"envFile": ".env"
}
}
}

Each project keeps its own .env with the right credentials. After setting this up, disable the plugin’s copy in Settings > Tools & MCP so you’re not running duplicates.

More on workspace MCP config: MCP