Integrations
Integrations
Built-in services, provider accounts, agent skills, MCP servers, and API keys for your workspace and projects.
Workspace Integrations manages reusable settings for your personal workspace; a team workspace has its own Integrations page. In a web project, /integrations opens Project setup, which has the same tabs for that project.
| Tab | Purpose | Guide |
|---|---|---|
| Built-in | Your pre.dev API key, Payments, and sign-in apps that pre.dev sets up for every project | Built into every app |
| Connections | Authorize a provider account and choose which account a project uses | Provider connections |
| Agent Skills | Reusable instructions for the coding agent | Agent skills |
| MCP Servers | Tools exposed by an external MCP server | External MCP servers |
| API Keys | Third-party credentials and environment variables for your apps | Service API keys and environment variables |
Connection selection
A personal project uses its personal workspace’s connections. A team project uses its team’s connections. Each workspace can connect multiple accounts for the same provider.
| Project setting | Account the project uses |
|---|---|
| No account pinned | The workspace default for that provider |
| Account pinned | The pinned account, which takes precedence over the workspace default |
In either case, connect or reauthorize the account if its connection is missing or expired.
In Connections, leave a provider on workspace default or pin an account for this project. Connecting an account from Project setup selects it for that project.
Skill and MCP scope
Personal projects inherit personal entries and can add project-specific entries. A project entry with the same name takes precedence over its personal default. Organization entries remain shared within the organization, including when managed from a team project.
The CLI’s /skills, /mcp, and /integrations panels manage or display personal entries, and /skills add and /mcp add create them. Use the web for team configuration and project overrides.
Connect pre.dev to another agent
To give an external assistant pre.dev’s specification and browser tools, use the product MCP server. That is a separate direction of integration from adding an external MCP server to the Coding Agent.