Skip to main content
Glama
Sign In
mcp-divineapi-docs

mcp-divineapi-docs

by Dinesh-Gahlot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Divine API - Documentation MCP Server

A public, read-only MCP server that answers "how do I use the DivineAPI REST API". It serves the already-public developer documentation: every endpoint, its parameters, its response fields, the global auth and error rules, and real captured example responses.

This server does NOT call the astrology APIs and needs NO credentials. It is a reference, not a data source. To actually run astrology requests, use the divineapi SDK or the data MCP servers:

  • Indian / Vedic: https://mcp.divineapi.com/indian/mcp

  • Western: https://mcp.divineapi.com/western/mcp

  • Horoscope, Tarot and Numerology: https://mcp.divineapi.com/horoscope/mcp

Public endpoint

https://mcp.divineapi.com/docs/mcp

No API key, no auth token, no OAuth. Just connect.

Related MCP server: pancake-api-mcp

Tools (5)

Tool

What it does

search_docs(query, limit=8)

Case-insensitive keyword search across every endpoint card; returns the top matching cards (most query tokens first).

get_endpoint(path)

The full reference card for one exact path, or the closest match / a "did you mean..." list.

list_endpoints(category="")

Every path [host] line, optionally filtered to a category (Indian, Western, Numerology, PDF, Horoscope, Lifestyle, Calculators).

get_playbook()

The global rules: auth, error semantics per host, birth params, horoscope selectors, field formats, house systems, and what not to do.

get_example(path)

A real captured example response body for the path (version-agnostic slug fallback), or a pointer to the card's returns: line.

Data sources

  • docs-pack.txt is fetched live at startup from https://developers.divineapi.com/docs-pack.txt (10s timeout); on failure the server falls back to the bundled snapshot shipped in this repo.

  • examples.json is a map of normalized_path -> example response body, generated from the published Postman collection by build_examples.py. Regenerate it with:

python3 build_examples.py "/path/to/DivineAPI_Collection_with_examples_Final Version.json"

Run locally

python -m venv .venv && source .venv/bin/activate
pip install ".[http]"

# stdio (for Claude Desktop, Cursor, etc.)
divineapi-docs-mcp

# HTTP (streamable-http on :8000)
MCP_TRANSPORT=http uvicorn server:app --host 0.0.0.0 --port 8000

Deploy

Mirrors the DivineAPI data MCPs. The container runs uvicorn server:app on port 8000; docker-compose maps host port 8004 -> 8000.

docker compose up -d --build

Documentation: https://developers.divineapi.com

Available Tools

5 tools
get_endpointA

Return the full reference card for one endpoint path.

Give an exact path such as /indian-api/v1/auspicious-timings. If the path is not an exact match, the closest single endpoint (substring on the last path segment) is returned, otherwise a short "did you mean..." list of candidates. The card lists the host, summary, params (with * for required and example values), and the top-level response fields (returns: line).

Inputs: path (required). Returns: result

get_exampleA

Return a real captured example response body for an endpoint path.

Uses the bundled examples (with a version-agnostic slug fallback, so an example captured at /api/v2/x also answers for /api/v3/x). If no example was captured for the path, points you to the card's returns: line instead.

Inputs: path (required). Returns: result

get_playbookA

Return the global DivineAPI usage rules (the docs-pack header).

Covers authentication (Bearer token + api_key form field), error semantics per host, the standard birth params, horoscope selectors, field formats, house systems, SDK installs, the MCP server URLs, and a "what not to do" list of common mistakes. Read this before constructing any request.

Inputs: no named parameters. Returns: result

list_endpointsA

List endpoint paths with their hosts, optionally filtered by category.

With no argument, lists every endpoint as "path [host]" lines. Pass a category substring (case-insensitive) to filter, e.g. "Indian", "Western", "Numerology", "PDF", "Horoscope", "Lifestyle", or "Calculators".

Inputs: category. Returns: result

search_docsA

Search the DivineAPI docs by keyword and return the matching endpoint cards.

Case-insensitive token scan over every endpoint reference card. Cards that match more of the query's tokens rank first. Returns up to limit whole cards (path, summary, params, returns). Use this when you know roughly what you want ("auspicious timings", "natal wheel", "love compatibility") but not the exact path.

Inputs: query (required), limit. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_endpoint returns reference cards, get_example returns example responses, get_playbook returns global rules, list_endpoints lists paths, and search_docs searches by keyword. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_endpoint, get_example, get_playbook, list_endpoints, search_docs. The naming is predictable and uniform.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of serving API documentation. It provides essential functions for retrieving endpoint details, examples, listing, searching, and understanding rules without being excessive or insufficient.

    Completeness5/5

    The tool set covers all key documentation activities: listing endpoints, searching by keyword, retrieving detailed reference cards, accessing example responses, and obtaining usage rules. There are no obvious missing features for the domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • RootApp Documentation MCP

      cyberofficial
      A
      license
      Not graded
      quality
      D
      maintenance
      Serves RootApp documentation files with search and retrieval capabilities, enabling users to access specific docs, browse directory structure, and search across file names and content.
      AGPL 3.0
    • Ravensight documentation MCP

      Ravensight documentation MCPofficial

      Reality-Software-Entertainment
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to search and read public Ravensight documentation over unauthenticated remote HTTP, retrieving cited excerpts and Markdown sections with revision-aware pagination. Provides a browsable index of document IDs and sections, with read-only, free access that cannot touch customer studios or player data.
      MIT