MCP servers added for your stack

What stack-scoped servers are

Stack-scoped MCP servers are the ones Paqad lists only for certain frameworks. MCP servers are helper programs an AI coding tool can call for information; Paqad only writes their names into a file per host tool and never starts or contacts them (see MCP servers and Paqad).

Each stack pack can declare servers in an mcp_defaults list. An entry either always applies (when: always) or applies only when a trait, an add-on library such as Tailwind or Prisma, is detected (when: when_trait).

Servers listed for each built-in pack

This table combines the pack's mcp_defaults with Paqad's built-in rules (figma for every framework, and database-inspector for Laravel and Flutter). "With trait" means the server is listed only when that trait is detected.

Pack	Always listed	Listed with trait
angular	figma	none
astro	figma	none
django	figma, database-inspector	none
dotnet	figma	database-inspector (ef-core)
express	figma, database-inspector	none
fastapi	figma, database-inspector	none
flask	figma	none
flutter	figma, database-inspector, dart-mcp	none
go-web	figma, database-inspector	none
kotlin-android	figma	database-inspector (room)
laravel	figma, database-inspector	laravel-boost (boost), tailwind-mcp (tailwind)
nestjs	figma	database-inspector (prisma or typeorm)
nextjs	figma	tailwind-mcp (tailwind), database-inspector (prisma)
node-cli	figma	none
node-library	figma	none
node-service	figma, database-inspector	none
rails	figma, database-inspector	none
react	figma, vite-inspector, react-router-mcp	tailwind-mcp (tailwind)
rust-web	figma, database-inspector	none
spring-boot	figma, database-inspector	none
svelte	figma	none
vue	figma, vite-inspector, vue-router-mcp	tailwind-mcp (tailwind)

A project that matches several packs gets the combined list, with each name once. You can turn any of these off, or turn on another of the eight known names, in the project profile (see Default MCP servers).

How a pack declares a server

This is the mcp_defaults list from the built-in Laravel pack:

mcp_defaults:
  - name: laravel-boost
    when: when_trait
    trait: boost
  - name: tailwind-mcp
    when: when_trait
    trait: tailwind

Each entry has only name, when and, for when_trait, trait. There is no field for a start command, arguments or a scope.

Limits when you write your own pack

• Only the eight known names work. paqad-ai packs validate warns about any other name, saying it "will be treated as custom", but in 1.91.1 such a name is left out of the MCP files entirely.
• Only a global override counts. When Paqad builds the server list it reads built-in and global packs, not packs in the project's .paqad/packs/ folder. See Which pack wins when names match.
• The trait must be one the project profile recognises. when_trait entries are matched against the traits recorded in your project profile, and only trait names from Paqad's fixed list count. A trait name you invent in your own pack never switches a server on.

Data and external services

Listing a stack-scoped server does not install or run it, and Paqad sends nothing anywhere when it writes the list. If you set up one of these servers in your host tool, what it reads and where it sends data depends on that program. Check each one before you connect it, especially servers such as figma that exist to work with an online service.