# How do we configure workspace-specific plugin MCP servers

**URL:** <https://forum.cursor.com/t/how-do-we-configure-workspace-specific-plugin-mcp-servers/161660>\
**Category:** Help\
**Tags:** plugins, mcp\
**Created:** [May 26, 2026, 9:35pm UTC](https://forum.cursor.com/t/how-do-we-configure-workspace-specific-plugin-mcp-servers/161660 "2026-05-26T21:35:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![aslangoldenhour](https://avatars.discourse-cdn.com/v4/letter/a/4bbf92/32.png) [@aslangoldenhour](https://forum.cursor.com/u/aslangoldenhour)\
**Post date:** [May 26, 2026, 9:35pm UTC](https://forum.cursor.com/t/how-do-we-configure-workspace-specific-plugin-mcp-servers/161660/1 "2026-05-26T21:35:48Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [May 27, 2026, 7:58am UTC](https://forum.cursor.com/t/how-do-we-configure-workspace-specific-plugin-mcp-servers/161660/6 "2026-05-27T07:58:54Z")

</div>

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`:

```auto
{
"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`:

```auto
{
"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](https://cursor.com/docs/mcp)

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 25, 2026, 9:35pm UTC](https://forum.cursor.com/t/how-do-we-configure-workspace-specific-plugin-mcp-servers/161660/8 "2026-06-25T21:35:51Z")

</div>

This topic was automatically closed after 30 days. New replies are no longer allowed.