NoCRM.io
noCRM.io is a lead management software designed to help sales teams track and close deals efficiently.
Verdict
Common use cases
- Log inbound leads from chat without leaving Slack
- Tag hot prospects during discovery calls
- Move deals to standby after scheduling follow-ups
- Reassign leads when reps go on vacation
- Append call notes to lead descriptions in real time
Integration
- Vendor
- NoCRM.io
- Category
- crm
- Auth
- API_KEY
- Tools
- 9
- Composio slug
nocrm_io
Tools
- Add a tag to a lead
Tool to add a tag to a lead. use when you need to assign one or more tags to a specified lead via nocrm.io.
- Append to lead's description
Tool to append text to the lead's description. use when you need to add context incrementally without overwriting. example: append 'left voicemail' to lead 1234.
- Assign Lead to User
Tool to assign a lead to a user. use when reassigning a lead to the correct owner to trigger assignment notification.
- Change lead status standby
Tool to change a lead's status to 'standby'. use when scheduling follow-up after determining the next contact should occur in a set number of days.
- Change Lead Status to Cancelled
Tool to change a lead's status to 'cancelled'. use after confirming no further follow-up is needed and the lead should be marked as cancelled.
- Create Lead
Tool to create a new lead. use when adding a fresh prospect to your pipeline via nocrm.io. example: create a lead titled 'acme corp' assigned to a user.
- Delete Leaddestructive
Tool to delete a lead. use when you need to permanently remove a specific lead after verifying it is no longer needed.
- Duplicate Lead
Tool to duplicate a lead. use when cloning an existing lead into a new step without overwriting original.
- List All Teams
Tool to retrieve all teams. use when you need to fetch every team and its members from nocrm.io.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select NoCRM.io from the catalog. 3. Log into your NoCRM.io account, go to Settings > API, and generate a new API key with 'Leads: Read & Write' permissions. 4. Copy the key and paste it into Switchy's API Key field, then click 'Connect'. 5. Switchy will verify the connection by fetching your pipeline structure — you'll see a green checkmark when ready. 6. Open any Space, type '@NoCRM.io create a lead titled Test Prospect assigned to me', and send. 7. Check your NoCRM.io pipeline — the new lead should appear within seconds. 8. If the lead doesn't appear, revisit Settings > API in NoCRM.io and confirm the key hasn't expired and has write scope enabled.
What teammates see: by default, memories from NoCRM.io are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Log New Lead
@NoCRM.io create a lead titled 'Acme Corp - Q1 Expansion' assigned to Sarah with the tag 'enterprise' and description 'Referred by existing customer, interested in annual plan'.Open in a Space →
Update Deal Status
@NoCRM.io change lead 4521 to standby status with follow-up in 7 days, then append 'Demo scheduled for next Tuesday' to the description.Open in a Space →
Tag by Segment
@NoCRM.io add tags 'healthcare' and 'mid-market' to lead 3389.Open in a Space →
Reassign Ownership
@NoCRM.io assign lead 2207 to Mike and append 'Reassigned from Jordan due to territory realignment' to the description.Open in a Space →
Mark Lead Lost
@NoCRM.io change lead 1893 to cancelled status and append 'Chose competitor after final proposal' to the description.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@nocrm show me all leads tagged 'enterprise' that are currently in standby status and haven't been contacted in over 30 days
Found 7 leads matching your criteria: • Acme Corp (standby since March 3, assigned to Sarah) — last contact 42 days ago • GlobalTech Industries (standby since Feb 28, assigned to Mike) — last contact 35 days ago • Enterprise Solutions Ltd (standby since Feb 15, assigned to Sarah) — last contact 48 days ago [5 more entries] All leads are tagged 'enterprise' and scheduled for future follow-up. The oldest standby is 48 days without contact.
This example demonstrates NoCRM.io's filtering and search capabilities across lead metadata. The MCP requires read access to leads and tags. Response format depends on your pipeline configuration — step names, custom fields, and tag taxonomies vary by account setup.
@nocrm create a new lead for 'Vertex Systems' assigned to Jamie, add tags 'inbound' and 'demo-requested', and append a note that they came from the webinar on May 15th
Lead created successfully: • Title: Vertex Systems • Assigned to: Jamie Rodriguez • Tags applied: inbound, demo-requested • Description: 'Inbound inquiry — attended webinar on May 15th, requested product demo during Q&A session.' • Status: New (default step) • Lead ID: #8472 Jamie will receive an assignment notification. The lead is now visible in your pipeline's first step.
This chains three write operations (create, tag, append) in one prompt. The MCP executes them sequentially — if tagging fails due to a typo, the lead still exists but lacks tags. Verify user names match your NoCRM.io team roster exactly, or assignment will fail silently.
@nocrm review all leads I created this week, identify which ones have no follow-up activity scheduled, and move them to standby for 7 days with a note explaining why
Analyzed 12 leads created by you since May 12th. Found 4 with no scheduled follow-up: • Moved lead #8401 (Pinnacle Co) to standby for 7 days — appended note: 'Awaiting budget approval confirmation before next contact.' • Moved lead #8419 (Streamline Inc) to standby for 7 days — appended note: 'Decision-maker on vacation until May 27th per gatekeeper.' • Moved lead #8455 (Apex Partners) to standby for 7 days — appended note: 'Requested pricing comparison; following up after internal review period.' • Moved lead #8467 (Catalyst Group) to standby for 7 days — appended note: 'Warm lead but timing unclear; checking back mid-month.' Remaining 8 leads already have active tasks or standby dates set.
This showcases AI reasoning layered over NoCRM.io's data — the MCP fetches leads, the AI identifies gaps in your workflow, then executes bulk status changes with context. Each standby action triggers NoCRM.io's reminder system. The 'why' notes are AI-inferred from lead history, not verbatim CRM data.
Use-case deep-dives
When NoCRM.io wins for fast lead assignment and tagging
A 6-person outbound sales team gets 40-60 inbound leads a week from web forms and partner referrals. The ops lead uses Switchy to triage each morning: read the lead title and source tag, assign to the right rep based on territory or vertical, append a quick note like 'warm intro from partner X', and tag for follow-up cadence. NoCRM.io's 9 tools cover the full handoff loop—create, assign, tag, append—without opening the CRM UI. This works cleanly until you hit 15+ reps or need complex routing logic (round-robin, weighted queues); at that scale, you want a dedicated automation layer, not a chat workspace. If your team is under 10 and lead volume stays under 100/week, this MCP keeps morning triage under 15 minutes and every rep sees context the moment they open their pipeline.
Why the standby-status tool matters for solo consultants
A solo consultant or 2-person agency runs 8-12 discovery calls a week. After each demo, they know the prospect needs 2 weeks to review internally or won't decide until next quarter. Instead of setting a calendar reminder and losing the thread, they use Switchy to change the lead status to standby with a 14-day or 90-day delay, then append the demo outcome to the description. NoCRM.io's standby tool surfaces the lead automatically when the wait period ends, so nothing falls through the cracks. This scenario breaks down if you're managing 50+ active deals at once—you'll want a full CRM with pipeline stages and weighted forecasting. But for consultants closing 2-4 deals a month, the standby workflow in Switchy replaces a messy spreadsheet and keeps follow-up disciplined without heavyweight CRM overhead.
When bulk lead operations justify the NoCRM.io MCP
A 4-person marketing team collects 200 business cards at a trade show, imports them as leads, then spends the next week deciding which are real prospects and which are tire-kickers. They use Switchy to batch-process: duplicate high-value leads into a 'hot' step, tag by industry or use-case, append booth-conversation notes, and cancel the obvious no-fits. The duplicate and delete tools let them reshape the pipeline without clicking through 200 lead pages. This workflow pays off when you're processing 50+ leads in a sitting; for everyday one-off lead edits, the MCP is overkill compared to just opening NoCRM.io. If your team runs 3+ events a year and each event dumps 100+ leads into the funnel, the MCP cuts post-event cleanup from 6 hours to under 2.
Frequently asked
What does the NoCRM.io MCP do in Switchy?
It lets your AI agents create leads, update descriptions, reassign ownership, change statuses (standby, cancelled, won), add tags, and duplicate records — all without leaving the chat. Think of it as giving your team's AI direct access to your sales pipeline so you can log prospect activity, triage inbound, or prep follow-ups in natural language instead of clicking through the NoCRM interface.
Do I need admin access to connect NoCRM.io?
You need an API key from NoCRM.io, which typically requires admin or account-owner permissions to generate. Once you paste that key into Switchy, any workspace member you grant access to this MCP can create and modify leads on behalf of your NoCRM account. If your NoCRM plan restricts API access, you won't be able to connect it at all.
Can the MCP update custom fields or attach files to leads?
No. The nine tools exposed cover core lead lifecycle actions — create, assign, tag, status changes, description appends, duplication, and deletion — but custom fields and file attachments aren't supported. If you need to log a custom data point, append it to the lead's description field as plain text, then update the custom field manually in NoCRM's UI later.
Why use this instead of the NoCRM.io web app or Zapier?
The MCP lives inside your AI chat, so your team can say "create a lead for Acme Corp, assign it to Sarah, tag it enterprise" in one sentence instead of switching tabs or building a multi-step Zap. It's faster for ad-hoc pipeline updates during calls or Slack threads. For scheduled bulk imports or complex conditional logic, stick with Zapier or the NoCRM API directly.
Who on the team should connect the NoCRM.io MCP?
Whoever owns your NoCRM account and can generate an API key should do the initial connection. After that, grant MCP access only to team members who need to create or modify leads — typically sales reps, SDRs, or ops. Everyone else can still read lead data the AI surfaces in chat without needing direct MCP permissions, keeping your pipeline secure.