Nimble CRM

com.nimble.appPublished by app.nimble.comOfficial publisherv1.1.1Updated Nov 5, 2026

Connect AI assistants to Nimble CRM to access and work with customer relationship data.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that connects an AI assistant to Nimble CRM so it can access and work with customer relationship data.

What you can do
  • Access and work with Nimble CRM customer relationship data from the assistant.
  • No individual tools are listed, so the exact actions available are not documented here; the server is described only as giving assistants access to CRM records.
When to use it
Useful when you want an assistant to work with the customer and contact data already stored in your Nimble CRM account, for example while drafting outreach or reviewing relationship information, without switching apps.
Requirements
A remote server reached at the provider's endpoint over streamable HTTP; no local package or environment variables are declared. OAuth authentication is required, so a Nimble CRM account and an OAuth sign-in flow are needed.
Before you install
The server works with customer relationship data, which is typically personal and business-sensitive; the specific read or write capabilities are not documented, so assume it may change records. Access is granted through OAuth to your Nimble account, and data is handled by the third-party provider.

Installation

In SourceWeft

  1. Open Nimble CRM in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.nimble.app%2Fnimble-crm/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nimble-crm": {
      "type": "http",
      "url": "https://app.nimble.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.1LatestNov 5, 2026
  2. v0.1.0-beta.1Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.