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: fastest setup

Run these commands in a terminal. The second command opens NoClutterCRM in your browser so you can sign in and approve access:

codex mcp add nocluttercrm --url https://nocluttercrm.com/mcp/nocluttercrm
codex mcp login nocluttercrm
codex mcp list

1. During browser login, use the NoClutterCRM account whose workspace and brand permissions Codex should inherit.
2. Review the user, workspace, redirect destination, capabilities, brands, and write policy, then choose Connect.
3. After login succeeds, start a new Codex session and use /mcp to confirm that nocluttercrm is available.
4. Begin with a read-only prompt such as “List the NoClutterCRM brands I can access.”

Manual configuration

Instead of the add command, place this entry in ~/.codex/config.toml or a trusted project’s .codex/config.toml, then run codex mcp login nocluttercrm:

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

Connect my local Codex installation to the NoClutterCRM remote MCP server.

Server name: nocluttercrm
Transport: Streamable HTTP
URL: https://nocluttercrm.com/mcp/nocluttercrm
Authentication: OAuth

Run:
codex mcp add nocluttercrm --url https://nocluttercrm.com/mcp/nocluttercrm
codex mcp login nocluttercrm

Pause while I complete NoClutterCRM sign-in and consent in the browser. Never ask me to paste a password, cookie, access token, authorization header, or authorization code into chat. After login, run codex mcp list and confirm that nocluttercrm is enabled. Tell me to start a new Codex session, then begin with the read-only request: “List the NoClutterCRM brands I can access.”

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. Choose only the capabilities and brands this client needs. New connections start with read access only.
5. Keep Ask in NoClutterCRM for writes unless you deliberately want to block every write or let enabled writes run automatically.
6. Read the data-egress notice: CRM results can be processed by the client’s AI provider under your agreement with that provider.
7. 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:

With Ask in NoClutterCRM, the first write does not change CRM data. The assistant returns an approval link; review the exact fields in the Approvals tab, approve or reject them, and then let the client retry the unchanged call. An approval expires quickly, works once, and cannot authorize changed arguments. After execution, verify the returned record ID and state in NoClutterCRM.

Manage access

Choose what each connector can do

Open AI connectors in NoClutterCRM and expand Manage permissions on the connection you want to change. Each connection has independent controls for workspace context, CRM reading, contact and company updates, pipeline updates, tasks, brand access, and write approval. These grants can only narrow the connected person’s live role and brand permissions; they never add application permissions the person does not already have.

Revoke

Revoke access from the client

Open AI connectors, find the connection, and choose Revoke access. NoClutterCRM immediately revokes its access and refresh tokens while retaining the privacy-safe activity record. A new OAuth authorization is required before that client can use NoClutterCRM again.

Troubleshooting

Common beta blockers

Opening the MCP endpoint in a browser shows 405

This is expected. A browser sends a GET request, while the MCP transport accepts client messages over POST. Add the URL to Codex and start OAuth login instead of opening the endpoint directly.

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

Codex CLI callbacks on localhost, 127.0.0.1, or ::1 are supported. Other clients must use a reviewed HTTPS origin. Send the client name, version, and safe callback origin—not a token—to support.