Skip to main content
Connect an external MCP server when the agent needs tools from another service or your own system. To use pre.dev’s tools in another assistant, follow product MCP setup instead.

​
Add a server

  1. Open Project setup → MCP or MCP Servers in workspace Integrations.
  2. Paste a remote URL, a supported command, or the server configuration.
  3. Include the authentication headers or environment values required by that server.
  4. Use Test to check the handshake and advertised tools.
  5. Save and enable the entry.
Remote configuration example; replace the URL and credential with your server’s values:
Standard-input/output configurations use command, args, and env. The command runs in the agent’s execution environment; a path on your own laptop is not automatically available there. Compatibility depends on transport, authentication, and runtime requirements. Test the actual configuration before relying on its tools.

​
Scope and controls

Personal projects inherit personal MCP entries and can override a matching name. Organization entries are shared across the organization. See integration scope. In the CLI, /mcp lists personal entries and supports toggling or removal. Press o to add or configure entries on the web. On the web, use /integrations to open Project setup. Enable the servers needed for the task, and describe the operation you want the agent to perform. A successful connection test confirms tool discovery; individual calls can still fail because of provider permissions or service errors.