Connect Smplify MCP
OAuth 2.1 is now the recommended connection path for the hosted Smplify MCP service. Use it for Claude web, desktop, mobile, and ChatGPT app-style integrations. The manual bearer-token path remains available only for advanced developer-tool setups such as Codex, Cursor, VS Code, Claude Code, and Claude Desktop.
Connect with OAuth 2.1
Add https://mcp.smplify.com/mcp as your remote MCP server in Claude or ChatGPT. The client will redirect you to https://auth.smplify.com, complete the Smplify sign-in flow, and receive a Smplify-issued MCP token.
Smplify keeps the upstream Smplify API bearer token server-side in a private connector vault. That vault now uses AWS KMS-backed envelope encryption in production, stays on the internal Railway network, and feeds an upstream session lifecycle manager so expiring connections can be flagged before access breaks and expired ones fail closed with a reconnect-required state.
After you connect on claude.ai, ChatGPT, or desktop, that same connection can be reused on supported mobile clients. If the upstream Smplify session is nearing expiry, Smplify recommends reconnect before the encrypted bridge expires.
Connector URL: https://mcp.smplify.com/mcp OAuth issuer: https://auth.smplify.com
Advanced manual bearer-token setup
Expand this only if you need explicit bearer-token auth for developer tools such as Codex, Cursor, VS Code, Claude Code, or Claude Desktop.
Advanced manual bearer-token setup
Expand this only if you need explicit bearer-token auth for developer tools such as Codex, Cursor, VS Code, Claude Code, or Claude Desktop.
The sign-in form below talks directly to https://api.smplify.com from your browser. mcp.smplify.com does not proxy or store your username or password in the manual setup flow, but OAuth remains the preferred hosted path because it keeps day-to-day token handling out of local app configs.
Sign in and generate config
Enter your Smplify credentials and we will fetch the bearer token in the browser, then generate the MCP config immediately.
If you already have a bearer token, you can skip the credential step and paste it below.
See the hosted connector architecture
Expand to review the end-to-end service flow behind the OAuth path, private connector vault, KMS-backed storage, and tenant-aware execution model.
See the hosted connector architecture
Expand to review the end-to-end service flow behind the OAuth path, private connector vault, KMS-backed storage, and tenant-aware execution model.
Hosted connector architecture
The hosted OAuth path is now a six-step service flow rather than a raw token paste.
1. Client starts OAuth
Claude or ChatGPT points at https://mcp.smplify.com/mcp and discovers the MCP-domain OAuth metadata.
2. Smplify sign-in
auth.smplify.com handles OAuth sign-in and issues a Smplify-issued MCP token for the client.
3. Private token bridge
If upstream Smplify API access still needs a bearer token, the bridge is stored only in the private connector vault.
4. KMS-backed storage
The connector vault uses AWS KMS-backed envelope encryption in production and is not exposed as a public integration surface.
5. Session lifecycle checks
The lifecycle manager tracks ACTIVE, EXPIRING_SOON, RECONNECT_REQUIRED, and REVOKED before MCP refreshes or upstream calls continue.
6. Tenant-aware execution
The MCP gateway validates the Smplify-issued token, resolves the vault connection over the internal path, and enforces explicit tenant context for multi-tenant writes.
Installation Ready!
Your private configuration payload was generated locally in this browser session.
Set SMPLIFY_MCP_TOKEN once in your shell if you want to reuse the same token across Codex, Cursor, VS Code, and the safer Claude Code path.
This adds Smplify as a user-scoped remote MCP server in Claude Code, so it is available across projects without editing JSON manually.
This keeps the JWT out of Claude Code's stored config. Use the shared SMPLIFY_MCP_TOKEN export above, then add Smplify using Claude Code's JSON config with ${SMPLIFY_MCP_TOKEN} expansion.