Gopher

io.github.CourtimusPrimePublished by GitHub account CourtimusPrimev0.1.0Updated Oct 27, 2026

Lead intelligence layer for AI agents. Discover and enrich B2B prospects from natural language.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Gopher is a local MCP server that gives an AI assistant a lead-intelligence layer for discovering and enriching B2B prospects from natural language.

What you can do
  • Discover B2B prospects from natural-language requests
  • Enrich prospect and company records with additional lead data
  • Act as a lead-intelligence layer that an assistant can query while researching targets
  • Tool-level details are not published, so the exact operations are only described at this level.
When to use it
Useful when an assistant needs to build or enrich B2B prospect lists, for example for sales research, outreach preparation or account discovery, and you already have a Gopher account.
Requirements
Runs as a local stdio process installed from the npm package gopher-mcp, so Node.js is needed. Requires a Gopher API key supplied through the GOPHER_API_KEY environment variable; the optional GOPHER_API_BASE_URL variable defaults to the hosted Gopher API. Network access to that API is required.
Before you install
The server needs a Gopher API key, a secret that should be kept out of shared configuration. Prospect data is sent to and returned from the third-party Gopher API, so consider privacy and compliance rules for contact data. No tool list is published, so review what the tools actually do before use.

Installation

In SourceWeft

  1. Open Gopher in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.