# Horoscope [Health: Active]

**Category:** 🔮 Spirituality & Esoterica  
**Repository:** https://github.com/pipeworx-io/mcp-horoscope  
**GitHub Stars:** 0  
**npm Downloads (last month):** 459  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/horoscope

## Description
Horoscope MCP — wraps the keyless Horoscope App API.

## Tools
Capabilities this server exposes over MCP:

- **daily_horoscope** — Get the daily horoscope for a zodiac sign. Returns the prediction text for a given day (today, tomorrow, yesterday, or a specific YYYY-MM-DD date). Useful for "what is my horoscope today" style questions.
- **weekly_horoscope** — Get the weekly horoscope for a zodiac sign. Returns the prediction text covering the current week.
- **monthly_horoscope** — Get the monthly horoscope for a zodiac sign. Returns the prediction text for the current month plus challenging and standout days.

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

```json
"mcpServers": {
  "horoscope": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-horoscope"]
  }
}
```

## Documentation

## What the Horoscope MCP server does

The Horoscope MCP server gives AI clients access to horoscope predictions for a selected zodiac sign. It wraps the keyless Horoscope App API and exposes daily, weekly, and monthly reading functions through the Model Context Protocol.

Daily readings can target today, tomorrow, yesterday, or a specific date in `YYYY-MM-DD` format. Weekly readings cover the current week. Monthly readings cover the current month and include challenging days and standout days when returned by the underlying API.

This server fits assistants that need to answer questions about zodiac forecasts or retrieve horoscope text on demand. It does not require an API key for the Horoscope App API.

## How it works

The hosted service is available through Pipeworx at `https://gateway.pipeworx.io/horoscope/mcp`. An MCP client connects to that URL and discovers the available tools during initialization. The same gateway also provides shared Pipeworx meta-tools, including `ask_pipeworx`, `discover_tools`, `search_within`, and `remember`/`recall`. These shared tools are listed alongside the horoscope tools on the pack endpoint.

The full gateway is available at `https://gateway.pipeworx.io/mcp` when an installation needs every catalog pack listed directly. Both gateway URLs can reach the broader Pipeworx data catalog through `ask_pipeworx`; the difference is which pack is listed directly by the connection.

For applications that do not use an MCP client, Pipeworx provides HTTP tool endpoints such as `POST https://gateway.pipeworx.io/v1/tools/daily_horoscope`. Tool details can be inspected with the corresponding `GET` endpoint.

## Setup and configuration

Add the hosted URL to an MCP client configuration:

```json
{
  "mcpServers": {
    "horoscope": {
      "url": "https://gateway.pipeworx.io/horoscope/mcp"
    }
  }
}
```

Claude Desktop, Cursor, and Windsurf are named as supported client options in the documentation. Initial calls do not require an account.

The Horoscope MCP server also runs locally as a stdio package. Use the following configuration:

```json
{
  "mcpServers": {
    "horoscope": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-horoscope"]
    }
  }
}
```

Running `npx -y @pipeworx/mcp-horoscope` starts the local process directly. The local mode communicates over standard input and output and does not use the gateway or its shared meta-tools.

## Tools and capabilities

- `daily_horoscope`: Retrieves prediction text for a zodiac sign and a relative or explicit date.
- `weekly_horoscope`: Retrieves prediction text for the current week and a zodiac sign.
- `monthly_horoscope`: Retrieves the current month's prediction, including challenging and standout days.
- `ask_pipeworx`: On the hosted gateway, accepts a plain-language question and routes it to an appropriate catalog tool.

The three horoscope tools are the only tools exposed by the standalone package. The hosted pack endpoint includes the shared gateway tools in addition to them.

## Limitations and notes

The hosted pack endpoint does not provide a way to remove the shared Pipeworx meta-tools. If their schemas add more context than needed, the documentation recommends using the full gateway once rather than connecting to multiple pack endpoints.

The local package and hosted endpoint expose the same horoscope tools, but they differ in transport and scope. Local stdio mode contains no `ask_pipeworx` routing, while the gateway modes can route questions across the broader Pipeworx catalog.

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