Close Mcp

com.closePublished by close.comOfficial publisherv1.0.1Updated Oct 24, 2026

Close CRM to manage your sales pipeline. Learn more at https://close.com or https://mcp.close.com

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for Close CRM that lets an assistant work with your sales pipeline data through an OAuth-authorized connection.

What you can do
  • Connect an assistant to a Close CRM account for sales pipeline work.
  • The listing names no individual tools, so the exact actions are not documented here; expect CRM-style access to leads, contacts and opportunities within Close.
  • Access is granted through OAuth sign-in to the Close service.
When to use it
Useful when your team keeps sales pipeline data in Close CRM and you want an assistant to work with that data directly, instead of copying records into a chat by hand.
Requirements
A remote MCP endpoint at mcp.close.com, reached over streamable HTTP; no local package or runtime is needed. An OAuth sign-in to a Close CRM account is required. Network access to the endpoint is needed.
Before you install
The connection is authorized through OAuth against your Close account, so the assistant may be able to read or change real CRM records depending on the permissions granted; review the scopes before approving. No tool list is published, so what it can write, send or delete is not stated in advance.

Installation

In SourceWeft

  1. Open Close Mcp 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.close%2Fclose-mcp/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": {
    "close": {
      "type": "http",
      "url": "https://mcp.close.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

1
  1. v1.0.1LatestSep 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.