Stratos MCP
Built-in local MCP bridge in Stratos v1.7.1 (proprietary native macOS PHP & Laravel dev stack) for Cursor, Claude Code, Claude Desktop & Windsurf: site metadata & read-only DB schemas. (Linked repo contains setup docs & example configs only; MCP server runs inside Stratos.)
Documentation
Stratos MCP Setup Guide
Connect Cursor, Claude Code, Claude Desktop, or Windsurf to the MCP bridge built into Stratos, a native macOS PHP and Laravel development environment.
This repository contains documentation and example configuration only. It does not contain the Stratos application source, a standalone MCP server, a hosted endpoint, or an installable connector. The server runs inside the separately installed Stratos app. Stratos is proprietary; publishing these instructions does not change the app's license.
Requirements
- Stratos 1.7.1 or later, installed on macOS 13 or later (Apple Silicon or Intel).
- A project linked in Stratos and a coding agent with MCP support.
- Permission to share the selected context with that agent.
Download Stratos · Full MCP documentation · Pricing and current plan limits
Recommended setup
- Open Stratos → Tools → Local AI & MCP.
- Select a linked project. Enable only the permissions you need; start with schema access.
- Click Start bridge. The local endpoint is
http://127.0.0.1:9921/mcp. - Choose Install agent configuration… and select your client. Stratos merges its entry, preserves other servers, and backs up existing configuration. Copy-only configuration is also available.
- Reconnect the client or restart it if required. Ask it to inspect your project's tables or a specific table's schema.
The bridge defaults off and uses a private token for each session. After restarting it, reinstall or recopy the agent configuration to refresh that token. No public hosted Stratos MCP URL is required.
Manual configuration templates
Prefer the app's generated configuration: it supplies the current token and the actual app executable path. These examples document the configuration Stratos 1.7.1 generates; client support and settings may change with client versions.
| Client | Template | Destination |
|---|---|---|
| Cursor | cursor.example.json | Selected project's .cursor/mcp.json |
| Claude Code | claude-code.example.json | Selected project's .mcp.json |
| Claude Desktop | claude-desktop.example.json | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windsurf | windsurf.example.json | ~/.codeium/windsurf/mcp_config.json |
Replace REPLACE_WITH_CURRENT_STRATOS_SESSION_TOKEN using the configuration copied from the running bridge. This placeholder is a literal string, not an environment variable that the client automatically expands. Never publish the resulting real token. Merge the mcpServers.stratos entry into your existing file instead of replacing other entries.
Claude Desktop uses Stratos's bundled stdio relay. Its sample assumes /Applications/Stratos.app; if installed elsewhere, use the executable path generated by the app. No third-party relay package is needed.
Free and Pro
Free supports agent configuration, permitted linked-site metadata (stratos://sites / get_sites), and read-only database schema inspection (get_schema). SQLite, MySQL, and PostgreSQL schemas include table names, column types, primary keys, nullability, and foreign keys; schema tools do not return database rows or passwords. Metadata permission covers all linked sites, including project and Nginx paths.
Pro adds permitted runtime context, profiling context, and PHP/SQL/Artisan execution that requires native confirmation in Stratos. Every execution action, including SQL reads, requires review. All tool definitions remain discoverable on Free; a premium call returns PRO_REQUIRED, not paid data or execution. License and capability permissions are separate checks.
See tool reference, security and privacy, and troubleshooting.
Try a read-only request
Ask your agent: “Use Stratos to list this project's database tables, then inspect the users table if it exists. Do not execute SQL or PHP.”
For protocol inspection, examples/requests.json contains separate JSON-RPC message bodies for initialization, tool discovery, and schema inspection. It is a collection of examples, not an MCP batch request or a file to run as a script. Send each message separately to the local endpoint with the current Bearer token; let your MCP client handle normal initialization.
Support and contributions
Use this repository's issues for errors in these guides or placeholder configurations. Do not attach tokens, .env files, database contents, dumps, email, or webhook payloads. For app support, use the contact details on the Stratos site.
This guide is maintained by Stratos's creator. It does not imply endorsement by client vendors or the MCP project. Stratos is unrelated to Apache Stratos and Strato AG. No recommendation, directory acceptance, or indexing timeline is promised.