# GEOboom MCP [Verified owner] [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://www.geoboom.io/docs/mcp  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/geoboom-mcp

## Description
Link building and mention outreach from your AI agent, with the permissions the owner approves.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://www.geoboom.io/docs/mcp), copied verbatim. Run them in order; they are not an mcpServers config.

1. Add to Claude Code:

```sh
claude mcp add --transport http geoboom https://api.geoboom.io/mcp
```

2. Add to Claude Code:

```sh
claude mcp add --transport http geoboom https://api.geoboom.io/mcp \
  --header "Authorization: Bearer gbk_..."
```

## Documentation

## What GEOboom MCP does

GEOboom MCP gives an AI agent access to GEOboom workflows for link building and mention outreach. It is intended for marketing tasks where an agent needs to help identify, pursue, or manage opportunities related to links and brand mentions.

The server operates within permissions approved by the owner. That permission model keeps the agent’s available actions tied to the access the owner has granted, rather than treating every possible outreach action as automatically available.

## How it works

GEOboom MCP is accessed through a hosted MCP endpoint:

`https://api.geoboom.io/mcp`

An MCP-compatible client connects to that URL and uses the resulting server connection to make GEOboom capabilities available to an AI agent. The agent can then work with the server for link-building and mention-outreach tasks, subject to the permissions approved by the owner.

This hosted arrangement means the client connection points to GEOboom’s endpoint rather than a locally installed server process. The endpoint should be treated as the service address when configuring an MCP client.

## Setup and configuration

Configure the MCP client to connect to:

```text
https://api.geoboom.io/mcp
```

After the connection is established, the available GEOboom actions are governed by the permissions approved by the owner. Review those permissions before allowing an agent to perform outreach-related work, especially when the workflow can affect external link or mention activity.

The server is suited to clients that can connect to a hosted MCP endpoint. Client-specific configuration should use the endpoint above as the connection target.

## Tools and capabilities

GEOboom MCP supports two related marketing capabilities:

- Link-building workflows driven by an AI agent
- Mention-outreach workflows driven by an AI agent
- Permission-controlled access approved by the owner

These capabilities make the server relevant to agents handling off-site marketing work rather than general-purpose content generation or analytics.

## Limitations and notes

The server’s stated scope is link building and mention outreach through GEOboom. Agent access is limited by the permissions approved by the owner, so the resulting workflow depends on that authorization. The hosted endpoint is the connection point for clients using GEOboom MCP.

_Full upstream README: https://allmcps.com/mcp/geoboom-mcp/readme_

