Default MCP servers

The short answer

Paqad knows eight MCP server names. MCP servers are helper programs an AI coding tool can call for information (see MCP servers and Paqad). For every coding project with a detected framework, Paqad lists figma. For Laravel and Flutter projects it also always lists database-inspector. Everything else comes from your stack packs or your own project profile.

Paqad does not ship general-purpose file, git, shell or documentation-search servers, and it lists nothing for content-only projects.

The eight server names Paqad knows

Name	What it is expected to provide
figma	Design specifications, components and layouts from Figma.
database-inspector	Database schema, indexes, foreign keys and query plans.
laravel-boost	Laravel routes, models, services, middleware and configuration, through Laravel Boost.
dart-mcp	Flutter widgets, dependencies, assets and platform details.
vite-inspector	The Vite build graph, asset manifest and hot-reload settings.
react-router-mcp	The React Router route tree, lazy-loaded chunks and navigation boundaries.
vue-router-mcp	The Vue Router route tree, navigation guards and layout routes.
tailwind-mcp	Tailwind design tokens, utility classes and theme settings.

These are names and descriptions only. Paqad does not bundle these programs or say which published package should supply each name. Installing and running a server is done in your host tool.

How the list is built

1. For each framework in your project profile, add figma. For laravel and flutter, also add database-inspector.
2. Add the servers each matching stack pack declares in mcp_defaults. Some only apply when a trait (an add-on library) is detected. The per-stack results are on MCP servers added for your stack.
3. Add any server from the eight names that your project profile turns on.
4. Remove any server your project profile turns off.

Each name appears once, however many frameworks ask for it. This is a deterministic calculation; the AI plays no part in it.

Turning a server off or on for one project

Use the mcp section of .paqad/project-profile.yaml. Onboarding writes it as an empty list, servers: [].

mcp:
  servers:
    - name: figma
      enabled: false
    - name: react-router-mcp
      enabled: true
      config:
        mode: manual

• enabled: false removes a server from the list, even if a default or a pack added it.
• enabled: true adds a server that is not a default for your stack, as long as it is one of the eight names.
• Keys under config are copied into that server's entry in each MCP file. This is where you could add settings your host tool expects, such as a start command.

When changes take effect

Editing the profile does not change the MCP files straight away. They are rewritten the next time Paqad regenerates your host tool files, for example with paqad-ai update. The profile file itself is described on Project profile.

Does any default send data outside your machine

Not through Paqad. Listing a server writes a name and a description into a local file; Paqad starts nothing and contacts nothing. If you then set up a server in your host tool, that program decides what it sends. A Figma server, for example, works with Figma's online service by design. Because figma is listed for every framework, turn it off in the profile if your team does not use Figma and does not want it recommended.