Project

Agent credentials

Configure API keys for coding agents at the project level. See Agent credentials for details on connecting credentials and precedence rules.

Network access

Control which external domains your coding agents can access while running. See Network sandboxing for details on configuring access modes, custom rules, and trusted package registries.

MCP servers

Configure Model Context Protocol (MCP) servers to extend agent capabilities with custom tools and integrations. MCP servers allow agents to interact with external services, databases, and APIs during implementations. MCP server settings apply to all agents.

Playwright MCP

Playwright MCP gives agents the ability to control a headless browser. With it enabled, agents can:

• Navigate to your app's live preview
• Click links and buttons, fill out forms
• Take screenshots of the UI and send them back to you in the chat
• Check the JavaScript console for errors

This is useful when you want agents to verify that UI changes actually work. Instead of trusting that the code looks right, the agent can test it in a real browser and see what users would see.

Screenshots taken by agents appear as Artifacts in the chat. This makes it easy to review visual changes without running the app yourself.

To enable: Go to Project Settings > MCP Servers > Enable Playwright MCP.

Sentry MCP

Sentry MCP lets agents query your Sentry account directly. With Sentry MCP enabled, agents can look up actual errors with full stack traces, request data, and get user context.

To enable:

1. Go to Project Settings > MCP Servers > Enable Sentry MCP
2. Add your Sentry Access Token
   • Generate a token at sentry.io/settings/account/api/auth-tokens
   • Required scopes: event:read, org:read, project:read, team:read

Your token is stored encrypted and only passed to agents when Sentry MCP is enabled.

Custom MCP servers from your repos

Superconductor supports project-scoped MCP configuration stored in your repos. If your repo contains an MCP config file, Superconductor merges it into the agent's MCP configuration automatically. This lets you version-control MCP servers alongside your code so every agent gets the same tools without manual setup.

Each agent reads from its own config file format:

When there are conflicts between your repo config and the config Superconductor generates (e.g., from MCP servers enabled in Project Settings), Superconductor's config takes precedence.

Skills

Skills are built on an open standard and work with any Superconductor agent. Enable them from your project's Settings page. Once a skill is enabled, just ask your agent in the chat to generate an image, analyze a video, etc, and agents will use the relevant skill.

Available skills

• Video Understanding - Analyze videos up to an hour long. Supports local files (mp4, mov, webm, avi, mkv) and YouTube links.
• Audio Understanding - Transcribe and analyze audio up to 9.5 hours long. Supports mp3, wav, m4a, ogg, flac, and YouTube links.
• Image Generation - Generate images from text descriptions. Can use existing images or videos as style references.
• Video Generation - Create 4-8 second videos from text prompts. Supports image-to-video animation with native audio.
• Text to Speech - Convert text to natural-sounding speech. 30 voices, 24 languages, automatic language detection.

All skills require a Google Gemini API key configured at the workspace or project level.

Custom skills from your repos

You can also add custom skills by including them in your repo. Superconductor picks up agent-specific skill directories and makes them available:

The [repo]/.agents/skills/ path is part of the Agent Skills open standard and works across all agents. If multiple repos define a skill with the same name, the first repo (alphabetically) wins.

Skills use cases

Some examples of what you can do with Agent Skills:

• Create visual database structure diagrams automatically
• Analyze competitor demo videos to produce competitive analysis reports
• Generate multiple landing page redesign mockups from text descriptions
• Identify bugs from customer call recordings
• Extract customer testimonials from YouTube videos for your website

Treatment of PRs created outside of Superconductor

When you create a PR from Superconductor, links to the implementation and live preview are automatically posted in its description. You can enable the same behavior for PRs created outside of Superconductor—useful for open-source projects or teams where some contributors prefer to work outside Superconductor.

In Project Settings, you have two options:

• Do nothing (default) – External PRs won't trigger any Superconductor activity.
• Launch a preview environment – Superconductor creates a linked ticket and spins up a live preview with an agent ready to answer questions and make changes in the branch.

Development environment

Configure the development environment where agents run implementations. See Development environment for details on setting up your setup and startup commands, HTTP services, and other settings.