# noCRM.io MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## noCRM.io MCP

Read and manage sales leads, pipeline steps, and client folders in noCRM.io

- Record: https://musedirectory.ai/connector/nocrm-io-mcp
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/nocrm-io/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 148ms, checked 2026-10-29T22:41:16Z
- Endpoint: https://nocrm-io.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T22:41:16Z)
- Source: Found in the official MCP Registry (io.usefulapi/nocrm-io) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fnocrm-io

Connect to noCRM.io to view and manage sales leads, pipeline stages, comments, and client folders. Create new leads, update lead status and details, assign leads to team members, and track sales activity and history.

Example request: "Show me all unassigned leads and assign the most promising one to my top salesperson."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use noCRM.io MCP to help me. It is a free service with an MCP server at https://nocrm-io.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- nocrm_list_leads: List or search sales leads (noCRM.io's opportunities), newest first by default, with title, pipeline step, status, amount, probability, tags, owner, next reminder and the contact details in the description. Filter by status, step (names or ids, not mixed), owner, tags, email, sta
- nocrm_list_unassigned_leads: Leads that have no owner yet (for example web-form or API leads waiting to be handed to a salesperson). GET /leads/unassigned.
- nocrm_get_lead: One lead by id: title, step, status, amount, probability, tags, owner, client folder, team, reminder, and the full description with the contact's details. GET /leads/{id}.
- nocrm_list_lead_comments: The comments (notes, logged calls/meetings/emails) on a lead, newest first by default. GET /leads/{id}/comments.
- nocrm_list_lead_history: The timeline of a lead: creation, assignments, step and status changes, amount changes, comments and emails sent, with who did it and when. Filter by date range, action type or user. GET /leads/{id}/action_histories.
- nocrm_get_lead_duplicates: Leads that noCRM.io detects as possible duplicates of this lead (same email or key field). GET /leads/{id}/duplicates.
- nocrm_list_lead_attachments: File attachments on a lead (names, ids, sizes, links). GET /leads/{id}/attachments.
- nocrm_list_follow_ups: Post-sales processes (task checklists created from a template) of one lead OR of one user. Needs lead_id or user_id. Post-sales is a higher-edition feature (HTTP 403 otherwise). GET /follow_ups.
- nocrm_list_pipelines: The sales pipelines of the account (one unless the multiple-pipelines feature is on). GET /pipelines.
- nocrm_list_steps: The steps (stages) of the sales pipeline in order, with ids, positions and their pipeline. Use the ids or names when filtering leads or moving a lead. GET /steps.
- nocrm_list_users: The users (salespeople) of the account with name, email, phone, role (admin or not) and whether they are active or deactivated. Deleted users are included, flagged is_disabled. GET /users.
- nocrm_get_user: One user by id or email address. GET /users/{id}.
- nocrm_list_teams: Sales teams with their members and who manages each. The Teams feature must be on in the account (HTTP 403 otherwise). GET /teams.
- nocrm_list_client_folders: Client folders (accounts that group several leads), ordered by name by default. GET /clients.
- nocrm_get_client_folder: One client folder by id, with its contact fields and owner. GET /clients/{id}.
- nocrm_list_activities: The activity types (call, email, meeting and their outcomes) that can be set on a comment or reminder. GET /activities.
- nocrm_list_predefined_tags: The account's predefined tags (admin keys only; an HTTP 401 unauthorized_non_admin means the key lacks rights). GET /predefined_tags.
- nocrm_list_fields: The custom fields defined for leads or client folders. GET /fields.
- nocrm_create_lead: WRITE: create a new lead. The description holds the contact's details, one 'Label: value' per line (for example 'Firstname: Ada', 'Email: ada@example.com', 'Phone: ...'); noCRM.io reads those lines. Without user_id the lead is created unassigned; a pipeline step can only be set w
- nocrm_update_lead: WRITE: change a lead: title, status (won, lost, cancelled, todo or standby), pipeline step, amount, probability, star, estimated closing date, tags (replaces the lead's tag list), or append text to the description (existing description text is never replaced). Moving to standby n
- nocrm_assign_lead: WRITE: assign a lead to a user (id or email), replacing its current owner. The owner may get a notification from noCRM.io. POST /leads/{id}/assign.
- nocrm_add_lead_comment: WRITE: add a comment (an internal note) to a lead, optionally typed as an activity such as a call or meeting. It is visible to the lead's team in noCRM.io and sends nothing to the customer. Not idempotent. POST /leads/{id}/comments.
- nocrm_create_client_folder: WRITE: create a client folder (an account that groups leads). Not idempotent. POST /clients.
- nocrm_add_lead_to_client_folder: WRITE: file a lead under a client folder. POST /leads/{id}/add_to_client.

Screening checks:
- MCP handshake: pass (Answered in 148ms)
- Domain against threat feeds (Cloudflare security DNS): pass (nocrm-io.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (24 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)