Virtual Closer

com.virtualcloserPublished by virtualcloser.comOfficial publisherv1.0.0Updated Oct 31, 2026

See who replied and where your pipeline is stuck, from your own AI. Insurance agents. $55/30 days.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Virtual Closer that lets an assistant show which insurance prospects replied and where a sales pipeline is stuck.

What you can do
  • No tools are listed in the manifest, so capabilities come from the provider's description only.
  • Report who replied to outreach, viewed from the user's own AI assistant.
  • Surface where deals or leads are stuck in the pipeline.
  • Aimed at insurance agents' prospecting and follow-up work.
When to use it
Worth considering if you are an insurance agent using Virtual Closer and want pipeline and reply status visible inside your AI assistant instead of the product's own interface.
Requirements
A remote streamable HTTP endpoint at app.virtualcloser.com; no local package or runtime. OAuth authentication is required. A paid Virtual Closer subscription is implied by the listed price of $55 per 30 days.
Before you install
Access is tied to a paid subscription, so check billing terms before connecting. OAuth grants the assistant access to your pipeline and prospect reply data; review the scopes requested. No tool list is published, so what the assistant can read or change is unclear.

Installation

In SourceWeft

  1. Open Virtual Closer 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.virtualcloser%2Fvirtual-closer/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": {
    "virtual-closer": {
      "type": "http",
      "url": "https://app.virtualcloser.com/mcp/vc"
    }
  }
}

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.0LatestOct 31, 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.