Connect coding agents with Free schema and site context, or Pro runtime debugging and approved execution.

Requires Stratos 1.7.1 or later. Available in the current release.

Where to find MCP in the app

In the main Stratos window, select Tools in the sidebar, then Local AI & MCP. Choose a linked project, enable the permissions you want to share, and click Start bridge. An older installed app must be updated before this panel appears. Check your installed version in About.

Connect your coding agent

With the bridge running, choose Install agent configuration… and select Cursor, Claude Code, Claude Desktop, or Windsurf. Stratos merges its entry into the appropriate JSON file, preserves other servers, backs up existing configuration, and applies owner-only permissions. Copy-only configuration is also available.

Cursor: the selected project's .cursor/mcp.json.
Claude Code: the selected project's .mcp.json.
Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json, using Stratos's bundled stdio relay.
Windsurf: ~/.codeium/windsurf/mcp_config.json.

Reconnect or restart the agent after installation. The endpoint is http://127.0.0.1:9921/mcp and requires the current private Bearer token. Restarting the bridge rotates that token, so refresh the agent configuration. Keep generated credentials and their backups out of source control.

Free: read-only context

Enable linked-site metadata to expose stratos://sites or get_sites: domains, PHP versions, Nginx configuration paths, and known service status. This permission covers all linked sites.

Enable schema access for get_schema. With no arguments it lists table names; provide a table to inspect column types, primary keys, nullability, and foreign keys. Schema inspection supports local SQLite, MySQL, and PostgreSQL on Free. It returns no rows, passwords, or column default values.

Pro: runtime context and execution

read_dumps, read_http_requests, and read_logs provide bounded, selected-project context. HTTP exports exclude query strings, headers, and bodies; logs and dumps may contain sensitive application data.
read_mail and read_webhooks require separate app-wide permissions because capture records cannot be reliably assigned to a project. Webhook capture does not record the target application's response status.
analyze_performance returns completed SPX hotspots, slow HTTP requests, captured SQL samples, and repeated-query candidates. Repetition suggests an N+1 investigation; it is not proof. Instrumentation must already be collecting data.
run_tinker, query_database, and run_artisan queue actions for native confirmation in Stratos. Review the complete action and select Review & approve…. Poll execution_result with the returned request ID.

Every action, including SQL reads, needs confirmation. Approved actions use normal project/user permissions and can modify files or data, or contact services. This is project-scoped execution, not an OS sandbox. Stopping the bridge revokes agent access but does not undo an action already running. Server database connections stay on loopback; SQLite must be inside the selected project.

All tool definitions remain visible on Free. Premium calls return PRO_REQUIRED with upgrade guidance for $39/year Pro or $89 Founder Lifetime, plus a throttled in-app/native Upgrade action. Disabled permissions on Pro return PERMISSION_REQUIRED. Pro access is rechecked before execution.

Local Ollama and PostgreSQL vectors

Ollama model/status discovery is Free. Pro adds installation, owned-process start/stop, and an authenticated local proxy. Stratos stops only the Ollama process it launched; existing external processes retain their own lifecycle.

Enable the proxy, then select Configure Ollama in selected project's .env…. After confirmation, Stratos backs up the original file and sets OLLAMA_BASE_URL and OLLAMA_API_KEY without changing unrelated values. Your application must use these settings and send the key as a Bearer token. Refresh them after a bridge restart. The proxy supports bounded, non-streaming Ollama-native requests; it is not an OpenAI-compatible /v1 endpoint.

For pgvector, select a project configured for local PostgreSQL. Install the extension package if needed, then select Enable in selected project. The package must match your running PostgreSQL major version, and your database user needs extension privileges. A mismatch is reported without replacing the database server or its data.

Access and troubleshooting

The bridge defaults off, binds only to loopback, validates Host/Origin, and requires explicit permissions. Runtime tools use bounded polling rather than live SSE subscriptions. Unknown-site dumps are excluded, and missing telemetry is not reconstructed. If the port is occupied, stop the conflicting listener; if an agent cannot connect after restarting Stratos, reinstall its configuration with the new token.