Customer Guidance

Security Best Practices

Use this page to safely connect Smplify MCP in Claude Code, Claude Desktop, OpenAI Codex, Cursor, VS Code Agent Mode, and other trusted MCP-capable clients that support remote HTTP MCP with bearer headers or environment-backed tokens. This guidance complements the live security overview documented on /security.

Black and white illustration representing a completed security review and operational checklist

Protected access, human oversight, and safer operational boundaries for your connected MCP workflows.

Only connect to the official Smplify MCP endpoint: https://mcp.smplify.com/mcp. Treat copied setup commands, config snippets, and tokens as sensitive material.

Use trusted clients and installers

Only add Smplify MCP in clients and marketplaces that you and your organization trust.

Verify the exact domain before installing: mcp.smplify.com.
Prefer official Smplify docs and the generated setup snippets for Claude, Codex, Cursor, and VS Code.
Be cautious with third-party “one-click install” marketplaces and copied shell commands.

Understand token scope

Smplify MCP acts with the permissions of the bearer token you supply.

Prefer short-lived tokens whenever your environment allows it.
Rotate tokens regularly and after any suspected exposure.
Use the environment-variable setup path when you do not want raw JWTs stored in client config files.

Watch for prompt injection

Agents can be influenced by malicious content in tickets, notes, dashboards, emails, or documents connected to the same workflow.

Do not let external content automatically override your operating instructions.
Treat requests to export data, disable safeguards, or ignore policy as suspicious.
Review destructive or cross-system actions carefully before approval.

Keep a human in the loop

Human confirmation is strongly recommended for administrative actions that affect devices, users, or policies.

Require approval for device lock, wipe, unenroll, or authentication changes.
Require approval for tenant, LDAP, email, role, and policy updates.
For exploratory work, prefer review-first or read-only workflows.

Official Smplify domains

https://mcp.smplify.com/mcp — official Smplify MCP endpoint
https://mcp.smplify.com/setup — official setup guidance and generated client config snippets
https://mcp.smplify.com/security — security overview and control boundaries
https://api.smplify.com/api/v1 — upstream Smplify API base URL

Recommended customer practices

Keep URL-based token auth disabled unless a specific client truly cannot send headers.
Use short-lived, least-privilege bearer tokens whenever your environment allows it.
Document who can approve destructive actions and who owns token issuance and rotation.
Re-test setup flows after rotating tokens or updating client configuration.
Use trusted clients and keep tokens in header-based or environment-variable based setups whenever possible.

Black and white illustration representing explicit approval and completion of an administrative task

Use explicit approval steps for device, policy, role, and tenant actions.

Black and white illustration representing a security checklist and operational review

Keep a repeatable checklist for token rotation, audit verification, and workflow review.

What Smplify operates and enforces

Smplify operates both the hosted MCP gateway and the underlying Smplify Platform APIs. Requests run inside Smplify-managed controls and execute with the tenant-scoped bearer token you provide.

Smplify MCP does not proxy Smplify usernames or passwords through the setup portal.
The hosted service is designed to execute each request with the caller’s own bearer token, so access stays scoped to that token’s tenant permissions.
Smplify MCP does not override the permissions already embedded in your bearer token.
If you connect additional third-party tools to the same agent, those tools keep their own permissions and data-handling boundaries.