Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
noCRM (BYOK) icon

noCRM (BYOK)

Read your noCRM sales leads, pipelines, steps, client folders, users, teams and follow-ups with your own API key

Unify Dynamics LLC

Tools12read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProvidernoCRMunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which noCRM leads are still open and were updated this month?
Tools called
list_leads
Show noCRM lead 8113
Tools called
get_lead
Which noCRM leads are unassigned?
Tools called
list_unassigned_leads
What happened on noCRM lead 8113?
Tools called
list_lead_comments
What steps does my noCRM pipeline have?
Tools called
list_steps
Which pipelines exist in noCRM?
Tools called
list_pipelines

About

noCRM (BYOK) lets an AI assistant read your own noCRM data through the noCRM API with a key you supply (noCRM API key (created by an administrator)). Read-only: 12 tools (list_leads, get_lead, list_unassigned_leads, list_lead_comments, list_steps, list_pipelines, list_client_folders, get_client_folder, list_fields, list_users, list_teams, list_follow_ups). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.nocrm.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by noCRM. noCRM and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the noCRM API (*.nocrm.io) with a BYOK key; documentation: https://www.nocrm.io/api. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

12 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data12 tools
  • List leadsList leads with title, status, step, amount, probability, next action date, tags, owner and description.
  • Get leadGet one lead by ID with its status, step, amount, probability, dates, tags, description and the contact fields found in it.
  • List unassigned leadsList leads that belong to nobody yet (the Unassigned tab).
  • List lead commentsList the activity feed of one lead (notes, calls, emails) with author, activity type and date, newest first by default.
  • List stepsList pipeline steps in position order with the pipeline each belongs to.
  • List pipelinesList pipelines (a single one when multiple pipelines are not enabled on the plan).
  • List client foldersList client folders that group leads, with name, description and active flag.
  • Get client folderGet one client folder by ID.
  • List fieldsList the lead and client fields defined in the account, with type and position.
  • List usersList users with name, email, job title, admin flag, activation and disabled state.
  • List teamsList teams (needs the Teams feature, otherwise a 403 comes back).
  • List follow upsList post-sales tasks (follow-ups) of one lead or one user with status, counts and next action date.

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-nocrm.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 12 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-nocrm.connectorbay.com/mcp
RESTPOST https://byok-nocrm.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-nocrm.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your noCRM API key (created by an administrator) in the X-Upstream-Key header (get one at www.nocrm.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

noCRM connector: questions and answers

What is the noCRM connector?

noCRM (BYOK) lets an AI assistant read your own noCRM data through the noCRM API with a key you supply (noCRM API key (created by an administrator)). It is a hosted MCP server with 12 tools such as List leads, Get lead, List unassigned leads, List lead comments, List steps, List pipelines, published by Unify Dynamics LLC. It is independent and not affiliated with noCRM.

How do I connect noCRM to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-nocrm.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-nocrm.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-nocrm.json.

Do I need a noCRM account or API key?

Yes: this is a bring-your-own-key connector. Create a noCRM API key (created by an administrator) at https://www.nocrm.io/help/API and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is noCRM read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the noCRM connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Freshservice Org Config (BYOK)

Read your Freshservice departments, locations, agent groups, roles, workspaces, announcements and ticket, change and problem form fields with your own API key

Live · MCP + REST10 tools

Freshservice Projects (BYOK)

Read your Freshservice projects, project templates, fields, task statuses, priorities, task types, sprints and versions with your own API key

Live · MCP + REST8 tools

Freshservice Releases (BYOK)

Read your Freshservice release records, release form fields, requester groups and requester field definitions with your own API key

Live · MCP + REST5 tools

Freshservice Service Config (BYOK)

Read your Freshservice service catalog items and categories, SLA policies and business hours with your own API key

Live · MCP + REST6 tools

Freshservice Status Page (BYOK)

Read your Freshservice status pages: service components and their status, incidents, planned maintenances and status labels with your own API key

Live · MCP + REST6 tools

Frill (BYOK)

Read your Frill feedback board (ideas, comments, votes, topics, statuses, followers) and announcements with your own API key

Live · MCP + REST11 tools

Documentation

Back to top

noCRM (BYOK) — connector documentation

  • MCP endpoint: https://byok-nocrm.connectorbay.com/mcp
  • REST API: POST https://byok-nocrm.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-nocrm.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own noCRM noCRM API key (created by an administrator), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-nocrm.connectorbay.com/health · Tool schemas: https://byok-nocrm.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-nocrm · agent@connectorbay.com

What noCRM (BYOK) is for

noCRM (BYOK) lets an AI assistant read your own noCRM data through the noCRM API with a key you supply (noCRM API key (created by an administrator)). Read-only: 12 tools (list_leads, get_lead, list_unassigned_leads, list_lead_comments, list_steps, list_pipelines, list_client_folders, get_client_folder, list_fields, list_users, list_teams, list_follow_ups). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.nocrm.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by noCRM. noCRM and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which noCRM leads are still open and were updated this month?"
  • "Show noCRM lead 8113"
  • "Which noCRM leads are unassigned?"
  • "What happened on noCRM lead 8113?"
  • "What steps does my noCRM pipeline have?"
  • "Which pipelines exist in noCRM?"

What it does

  • list_leads: List leads with title, status, step, amount, probability, next action date, tags, owner and description. Filter by status, step, tag, owner or update date. Up to 100 per request; page with offset.
  • get_lead: Get one lead by ID with its status, step, amount, probability, dates, tags, description and the contact fields found in it.
  • list_unassigned_leads: List leads that belong to nobody yet (the Unassigned tab).
  • list_lead_comments: List the activity feed of one lead (notes, calls, emails) with author, activity type and date, newest first by default.
  • list_steps: List pipeline steps in position order with the pipeline each belongs to.
  • list_pipelines: List pipelines (a single one when multiple pipelines are not enabled on the plan).
  • list_client_folders: List client folders that group leads, with name, description and active flag.
  • get_client_folder: Get one client folder by ID.
  • list_fields: List the lead and client fields defined in the account, with type and position.
  • list_users: List users with name, email, job title, admin flag, activation and disabled state.
  • list_teams: List teams (needs the Teams feature, otherwise a 403 comes back).
  • list_follow_ups: List post-sales tasks (follow-ups) of one lead or one user with status, counts and next action date. Give lead_id or user_id.

BYOK key

You bring your own noCRM noCRM API key (created by an administrator) (https://www.nocrm.io/help/API). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.nocrm.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the noCRM API (*.nocrm.io) with a BYOK key; documentation: https://www.nocrm.io/api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by noCRM. noCRM and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your noCRM account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

noCRM (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What noCRM (BYOK) is. noCRM (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own noCRM data: Read your noCRM sales leads, pipelines, steps, client folders, users, teams and follow-ups with your own API key. You bring your own noCRM noCRM API key (created by an administrator); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one noCRM call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to *.nocrm.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If noCRM rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What noCRM receives. The request we make on your behalf, including the key and the arguments, under noCRM's own terms and privacy policy. noCRM acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer noCRM gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your noCRM data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. noCRM (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at noCRM at any time to end all access.

Children. noCRM (BYOK) is a general-audience service operated by the adult using the assistant, under noCRM's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

noCRM (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the noCRM (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. noCRM (BYOK) provides: Read your noCRM sales leads, pipelines, steps, client folders, users, teams and follow-ups with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own noCRM credentials and only access data you are allowed to access. noCRM's terms apply to your use of noCRM; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by noCRM. noCRM and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data noCRM returns, lightly trimmed; it may be incomplete, delayed or changed by noCRM. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your noCRM account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent noCRM's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; noCRM may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your noCRM key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action noCRM takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-nocrm

noCRM (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. noCRM (BYOK) never asks for them.

Get noCRM (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own noCRM noCRM API key (created by an administrator). Create one at https://www.nocrm.io/help/API, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to noCRM. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with noCRM.