Connect your AI to noCRM.io

What your AI can do with noCRM.io

Once connected, these tools appear automatically in your AI assistant:

• list_leadsread-only

  List leads, newest first by default. Filter by status (todo, standby, won, cancelled, lost), by pipeline step, by owner, by tags, or to starred leads only. Returns the lead summary; call get_lead for the full record.

• get_leadread-only

  Get one lead in full: description, contact details, amount, probability, step, tags, reminders and related user, team and client folder.

• create_leadwrite · needs approval

  Create a lead. It is owned by the connected user — noCRM does not allow assigning it to someone else with a personal login. Write action: subject to the confirmation guardrail when it is enabled.

• update_leadwrite · needs approval

  Update a lead: move it to another step, change its status (marking it won, lost or cancelled closes it), adjust amount, probability, tags, reminder or closing date. Write action: subject to the confirmation guardrail when it is enabled.

• list_lead_commentsread-only

  List the comments posted on a lead, oldest first.

• add_lead_commentwrite · needs approval

  Post a comment on a lead — the usual way to log a call, a meeting outcome or a next step. Write action: subject to the confirmation guardrail when it is enabled.

• list_stepsread-only

  List the pipeline steps a lead can sit in, in order. Use it before moving a lead so the step name is one the account actually has.

• list_pipelinesread-only

  List the sales pipelines of the account.

• list_client_foldersread-only

  List client folders — the customer records leads can be attached to once they are won.

• list_prospecting_listsread-only

  List the prospecting lists (the spreadsheets sales reps work through before a prospect becomes a lead).

• list_usersread-only

  List the users of the account, with their id — needed to filter leads by owner.

• delete_leadwrite · needs approval

  Delete a lead. It goes with its comments, its attachments and its history, and noCRM offers no way back — read it first if there is any doubt.

• delete_leadswrite · needs approval

  Delete several leads at once. Same finality as delete_lead, multiplied — this is the single most destructive call the connector exposes.

• add_lead_to_clientwrite · needs approval

  File a lead under a client folder, which is how noCRM groups everything belonging to one customer. Give the folder id, or a name to create the folder on the way.

• assign_leadwrite · needs approval

  Hand a lead to a salesperson. Give `userId` for a named person, or a `mode` to let noCRM pick: random, round_robin, or random_in_a_team with `teamId`.

• duplicate_leadwrite · needs approval

  Copy a lead into a new one, which is how a returning customer gets a second deal without losing the first.

• send_lead_email_from_templatewrite · needs approval

  Send an email to the lead's contact from one of the account's templates. This really leaves the building and cannot be recalled: the customer receives it.

• create_lead_follow_upswrite · needs approval

  Apply a follow-up template to a lead, which creates the whole sequence of tasks it describes.

• list_unassigned_leadsread-only

  List the leads nobody owns. The question a sales manager actually asks, and the one the general lead list answers badly.

• list_lead_duplicatesread-only

  The leads noCRM considers duplicates of this one, by contact details. Worth checking before creating anything, because a duplicated lead splits a customer's history in two.

• list_lead_historyread-only

  Everything that happened to a lead, in order: step changes, reassignments, status changes, with who did each and when. The record of how a deal actually went.

• list_lead_attachmentsread-only

  List the files attached to a lead — names, sizes and types. The contents are not returned.

• get_lead_attachmentread-only

  Get the metadata of one attachment, including the link noCRM serves it from.

• get_lead_business_cardread-only

  The lead's contact details on their own — name, company, phone, email — without the rest of the record.

• update_lead_commentwrite · needs approval

  Rewrite a comment on a lead.

• delete_lead_commentwrite · needs approval

  Delete a comment from a lead.

• list_follow_upsread-only

  List the follow-up sequences of the account, with their tasks and due dates.

• update_follow_up_taskwrite · needs approval

  Change one task of a follow-up — mark it done, move its date, rewrite it.

• create_client_folderwrite · needs approval

  Create a client folder — the box that gathers every lead belonging to one customer, with the billing and shipping details.

• get_client_folderread-only

  Get one client folder with its details and the leads filed under it.

• update_client_folderwrite · needs approval

  Change a client folder's details. Only the fields you send are touched.

• delete_client_folderwrite · needs approval

  Delete a client folder. The leads inside it are not deleted, they simply lose the folder.

• list_teamsread-only

  List the sales teams of the account, with their members.

• get_teamread-only

  Get one team and who is in it.

• create_teamwrite · needs approval

  Create a sales team.

• update_teamwrite · needs approval

  Rename a team.

• delete_teamwrite · needs approval

  Delete a team. Its members keep their accounts and their leads.

• add_team_memberwrite · needs approval

  Add a user to a team.

• remove_team_memberwrite · needs approval

  Take a user out of a team.

• get_userread-only

  Get one user: their name, email, role and whether the account is active.

• get_stepread-only

  Get one pipeline step by id, so a step id coming back on a lead reads as the stage it is.

• list_categoriesread-only

  List the lead categories of the account.

• list_predefined_tagsread-only

  List the tags the account has defined in advance. Reading these first keeps an assistant from inventing a tag that nobody else uses.

• list_fieldsread-only

  List the custom fields of the account, with their type and their possible values. Required before writing one: the names here are what create_lead and update_lead expect, and an invented one is ignored.

• list_activitiesread-only

  List the activity types the account uses — call, meeting, email — the vocabulary a logged action has to pick from.

• list_prospectsread-only

  List the prospects across the account's prospecting lists — the rows that have not become leads yet. Filter by list, by owner or by status to narrow it before paging, because the account's daily request budget is shared with everything else.

• list_prospects_called_fromread-only

  Find the prospect a phone number belongs to. This is what turns an incoming call into a name before anyone picks up.

• get_prospecting_listread-only

  Get one prospecting list with its columns and its counts.

• create_prospecting_listwrite · needs approval

  Create a prospecting list — the sheet a rep works through before anything becomes a lead.

• assign_prospecting_listwrite · needs approval

  Hand a prospecting list to a salesperson.

• comment_prospecting_listwrite · needs approval

  Leave a comment on a prospecting list.

• add_prospectwrite · needs approval

  Add a prospect to a prospecting list.

• update_prospectwrite · needs approval

  Change a prospect's own attributes — its status, its owner, its comment.

• update_prospect_fieldswrite · needs approval

  Change the column values of a prospect — the data of the sheet itself, as opposed to its status and ownership.

• create_lead_from_prospectwrite · needs approval

  Turn a prospect into a lead, which is the moment a name in a sheet enters the pipeline. The row keeps its place and gains a link to the lead.

• delete_prospectwrite · needs approval

  Delete a prospect from a prospecting list.

• comment_prospectwrite · needs approval

  Leave a comment on a prospect — what was said when nobody picked up.

• update_prospect_commentwrite · needs approval

  Rewrite a comment on a prospect.

Example prompts

Just ask your AI in plain language — it picks the right noCRM.io tool:

• “List leads, newest first by default. Filter by status (todo, standby, won, cancelled, lost), by pipeline step, by owner, by tags, or to starred leads only. Returns the lead summary; call get_lead for the full record — from noCRM.io, in plain language.”
• “Get one lead in full: description, contact details, amount, probability, step, tags, reminders and related user, team and client folder — from noCRM.io, in plain language.”
• “List the comments posted on a lead, oldest first — from noCRM.io, in plain language.”
• “List the pipeline steps a lead can sit in, in order. Use it before moving a lead so the step name is one the account actually has — from noCRM.io, in plain language.”

How it works

1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
2. Connect noCRM.io with your API key — each user connects their own account, credentials encrypted at rest.
3. Your AI instantly gets the noCRM.io tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does noCRM.io have an official MCP server?

You don't need one. Proxoria exposes noCRM.io to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official noCRM.io MCP server required.

What can my AI do with noCRM.io through Proxoria?

It gets 58 tools: list_leads, get_lead, create_lead, update_lead, list_lead_comments, add_lead_comment, list_steps, list_pipelines, list_client_folders, list_prospecting_lists, list_users, delete_lead, delete_leads, add_lead_to_client, assign_lead, duplicate_lead, send_lead_email_from_template, create_lead_follow_ups, list_unassigned_leads, list_lead_duplicates, list_lead_history, list_lead_attachments, get_lead_attachment, get_lead_business_card, update_lead_comment, delete_lead_comment, list_follow_ups, update_follow_up_task, create_client_folder, get_client_folder, update_client_folder, delete_client_folder, list_teams, get_team, create_team, update_team, delete_team, add_team_member, remove_team_member, get_user, get_step, list_categories, list_predefined_tags, list_fields, list_activities, list_prospects, list_prospects_called_from, get_prospecting_list, create_prospecting_list, assign_prospecting_list, comment_prospecting_list, add_prospect, update_prospect, update_prospect_fields, create_lead_from_prospect, delete_prospect, comment_prospect, update_prospect_comment. For example, list leads, newest first by default. filter by status (todo, standby, won, cancelled, lost), by pipeline step, by owner, by tags, or to starred leads only. returns the lead summary; call get_lead for the full record.

Is the noCRM.io connector read-only?

No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to noCRM.io.

How do I connect noCRM.io to my AI?

Create a Proxoria account, connect noCRM.io with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the noCRM.io tools.