# OmniForce [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/rmb/omniforce-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/omniforce

## Description
AI-search visibility: GEO audits, tracked prompts, competitors, citations.

## Tools
Capabilities this server exposes over MCP:

- **omniforce_geo_scan** — Audit a URL's GEO/AEO readiness → evidence-based score + findings.
- **omniforce_get_brand** — The tenant's brand profile.
- **omniforce_list_prompts** — Queries monitored across answer engines.
- **omniforce_list_competitors** — Competitors tracked for the tenant.
- **omniforce_list_snapshots** — Recent radar runs (citation/visibility snapshots).
- **omniforce_list_reports** — Shareable visibility reports.
- **omniforce_account** — Plan tier, included allotments, current usage, available upgrades.
- **omniforce_upgrade** — Create a hosted checkout link to upgrade the plan.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "omniforce": {
    "command": "npx",
    "args": ["-y","@omniforce/mcp"],
    "env": {
      "OMNIFORCE_API_KEY": "",
      "OMNIFORCE_API_BASE_URL": "",
      "PORT": "",
      "OMNIFORCE_ANON_DAILY_LIMIT": "",
      "MCP_CTA_FOOTER": ""
    }
  }
}
```

**Requires environment variables:** `OMNIFORCE_API_KEY`, `OMNIFORCE_API_BASE_URL`, `PORT`, `OMNIFORCE_ANON_DAILY_LIMIT`, `MCP_CTA_FOOTER` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What OmniForce does

The OmniForce MCP server exposes selected OmniForce GEO and AI-search visibility functions through the Model Context Protocol. It supports two access levels: a keyless URL audit and authenticated tenant operations. The unauthenticated audit checks a URL's GEO/AEO readiness and returns a score with findings. Tenant tools read data associated with an OmniForce account, including its brand profile, monitored prompts, tracked competitors, visibility snapshots, and shareable reports.

The server also exposes account and upgrade operations. Account details include the current plan, included allotments, usage, and available upgrades. When a higher tier is needed, the upgrade tool creates a hosted checkout link for one of the supported tiers: solo, starter, growth, or scale.

For teams working in the 🎯 Marketing category, the OmniForce MCP server can bring existing AI-search monitoring data into an agent conversation without requiring a separate dashboard workflow.

## How it works

The server communicates with MCP clients over stdio when launched through the npm package. It can also run over Streamable HTTP for registries and hosted clients. The HTTP service exposes `/mcp`, plus health and server-card endpoints.

`omniforce_geo_scan` does not require authentication. The remaining tools require an OmniForce API key and read tenant data from the configured OmniForce API base URL. For HTTP requests, authentication is supplied per request with either an `Authorization: Bearer` header or an `x-api-key` header.

The server is read-only with respect to account data. It does not write to the OmniForce account; the upgrade operation creates a hosted checkout link rather than performing the purchase inside the server.

## Setup and configuration

The package can be started without a local install using `npx` and `@omniforce/mcp`. Add it to an MCP client's server configuration with the `npx -y @omniforce/mcp` command. Set `OMNIFORCE_API_KEY` when tenant tools are needed. Omitting the key leaves the keyless GEO scan available.

The API endpoint defaults to `https://api.omniforce.run`. Set `OMNIFORCE_API_BASE_URL` to use another base URL. From source, the documented workflow is to install dependencies, build the project, and run `node dist/index.js` for stdio operation.

For HTTP deployment, set a port and run the HTTP start script, or build and run the provided HTTP Docker image. Anonymous HTTP access to the GEO scan is rate-limited per IP and day; the documented default is 10 requests. `OMNIFORCE_ANON_DAILY_LIMIT` changes that limit, while `MCP_CTA_FOOTER=off` disables the anonymous upsell footer.

## Tools and capabilities

The OmniForce MCP server provides these tools:

- `omniforce_geo_scan`: Audits a URL for GEO/AEO readiness and returns an evidence-based score and findings.
- `omniforce_get_brand`: Retrieves the tenant's brand profile.
- `omniforce_list_prompts`: Lists queries monitored across answer engines.
- `omniforce_list_competitors`: Lists competitors tracked for the tenant.
- `omniforce_list_snapshots`: Lists recent citation and visibility snapshots.
- `omniforce_list_reports`: Lists shareable visibility reports.
- `omniforce_account`: Shows plan, allotments, usage, and available upgrades.
- `omniforce_upgrade`: Generates a hosted checkout link for a selected plan tier.

## Limitations and notes

Only the GEO scan is keyless. The monitoring, account, and upgrade tools need a tenant API key. The server does not describe a tool for adding competitors, changing prompts, editing brand data, or updating account settings. Anonymous GEO scans are subject to the configured daily limit.

The API key is sent only to the configured OmniForce API base URL. The repository identifies the project license as MIT.

_Full upstream README: https://allmcps.com/mcp/omniforce/readme_