Connect an AI assistant to NoClutterCRM.

Desktop app or IDE extension

1. Open Settings → MCP servers.
2. Choose Add server, select Streamable HTTP, and enter the endpoint above.
3. Name the server NoClutterCRM, save it, and restart the client when prompted.
4. Select Authenticate and complete the NoClutterCRM browser flow.

Codex CLI

Add this server to ~/.codex/config.toml or a trusted project’s .codex/config.toml:

[mcp_servers.nocluttercrm]
url = "https://nocluttercrm.com/mcp/nocluttercrm"
auth = "oauth"

Then start OAuth login:

codex mcp login nocluttercrm

See the official Codex MCP guide for the current client controls.

NoClutterCRM is not listed in the public Plugins Directory. Approved testers can add the remote server through ChatGPT developer mode when that feature is available to their account and workspace:

1. Open ChatGPT settings, select Security and login, and enable Developer mode.
2. Open Plugins, choose the add button, and create a connection using the endpoint above.
3. Review the tools ChatGPT discovers, then complete NoClutterCRM authentication.

Workspace policy can hide developer mode or prevent private connections. See OpenAI’s current connection guide.

Step 2C

Other MCP clients

A compatible client must support the MCP 2025-11-25 Streamable HTTP transport, OAuth Authorization Code with PKCE, protected-resource discovery, and dynamic public-client registration. Approval is case by case during the beta.

Step 3

Approve the connection carefully

1. Sign in to NoClutterCRM and complete recent password or passkey confirmation.
2. Confirm that the displayed NoClutterCRM user and workspace are correct.
3. Check the full redirect destination and confirm that you initiated the connection.
4. Read the data-egress notice: CRM results can be processed by the client’s AI provider under your agreement with that provider.
5. Choose Connect only when every detail is expected.

A dynamically registered client is labelled Unverified public client. Its self-supplied name is not publisher verification.

Step 4

Verify with a read before a write

Start with prompts that prove brand and record visibility without changing anything:

For a write, ask the assistant to summarize the exact proposed change first. After saving, verify the returned record ID and state in NoClutterCRM.

Disconnect

Remove access from the client

Use the client’s Disconnect, Remove, or Logout action first. Clients that support token revocation can revoke the current server token as part of that flow.

Troubleshooting

Common beta blockers

The endpoint returns “not found”

The global connector beta may be disabled. Confirm the rollout status with NoClutterCRM support.

Authorization says the workspace is unavailable

The workspace may be inactive or may not have the MCP entitlement. An owner should contact support.

A record is missing or a write is forbidden

NoClutterCRM rechecks your live brand membership and role permissions on every tool call. Verify the selected brand and your access in the CRM.

The OAuth callback or client is rejected

Only reviewed HTTPS origins and approved local loopback callbacks are allowed. Send the client name, version, and safe callback origin—not a token—to support.