Read noCRM.io leads, pipeline steps, comments and client folders; create, update and assign leads. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"nocrm-io": {
"url": "https://nocrm-io.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"nocrm-io": {
"type": "http",
"url": "https://nocrm-io.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your noCRM.io account and noCRM.io API key.
In noCRM.io open the Admin section, Integrations → API, and generate a key (admins only). The account name is the first part of your address: acme for https://acme.nocrm.io. The key acts with admin rights on that account and is used only to call the noCRM.io API on your behalf; it is never shown to anyone. noCRM.io allows 2000 API requests per day per account.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your noCRM.io account and noCRM.io API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the noCRM.io connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
nocrm_list_leads | read | 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, starred or a date range. Unassigned leads are excluded unless include_unassigned is true. GET /leads. |
nocrm_list_unassigned_leads | read | 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 | read | 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 | read | 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 | read | 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 | read | Find duplicate leads Leads that noCRM.io detects as possible duplicates of this lead (same email or key field). GET /leads/{id}/duplicates. |
nocrm_list_lead_attachments | read | List lead attachments File attachments on a lead (names, ids, sizes, links). GET /leads/{id}/attachments. |
nocrm_list_follow_ups | read | List post-sales 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 | read | List pipelines The sales pipelines of the account (one unless the multiple-pipelines feature is on). GET /pipelines. |
nocrm_list_steps | read | List pipeline 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 | read | 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 | read | Get user One user by id or email address. GET /users/{id}. |
nocrm_list_teams | read | 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 | read | List client folders Client folders (accounts that group several leads), ordered by name by default. GET /clients. |
nocrm_get_client_folder | read | Get client folder One client folder by id, with its contact fields and owner. GET /clients/{id}. |
nocrm_list_activities | read | List activity types The activity types (call, email, meeting and their outcomes) that can be set on a comment or reminder. GET /activities. |
nocrm_list_predefined_tags | read | 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 | read | List custom fields The custom fields defined for leads or client folders. GET /fields. |
nocrm_create_lead | write | Create lead WRITE: create a new lead. The description holds the contact's details, one 'Label: value' per line (for example 'Firstname: Ada', 'Email: [email protected]', 'Phone: ...'); noCRM.io reads those lines. Without user_id the lead is created unassigned; a pipeline step can only be set when the lead is assigned. Not idempotent: calling twice creates two leads. POST /leads. |
nocrm_update_lead | write | 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 needs remind_date. Only the fields you pass change. PUT /leads/{id}. |
nocrm_assign_lead | write | 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 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 client folder WRITE: create a client folder (an account that groups leads). Not idempotent. POST /clients. |
nocrm_add_lead_to_client_folder | write | Add lead to client folder WRITE: file a lead under a client folder. POST /leads/{id}/add_to_client. |
nocrm_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
nocrm_request_feature | Request a missing feature Tell usefulapi that the user needs something the noCRM.io tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
nocrm_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on noCRM.io (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
nocrm_cancel_subscription | Cancel the Pro subscription Cancel the caller's noCRM.io Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run nocrm_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this noCRM.io server only. Subscribe with nocrm_upgrade (it returns a Stripe Checkout link). Cancel any time with nocrm_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running nocrm_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by noCRM.io. The server calls the noCRM.io API with your own noCRM.io access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your noCRM.io account and noCRM.io API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your noCRM.io account and noCRM.io API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the noCRM.io API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in noCRM.io.
Yes, if you approve it. 6 of the 24 noCRM.io tools can create or change data. The other 18 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this noCRM.io server only. Cancel any time: Pro then runs to the end of the paid period. Run nocrm_usage_status to see how many calls you used.
Ask the AI to run nocrm_upgrade: it returns a Stripe Checkout link. To cancel, run nocrm_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with nocrm_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.