Codex + Occult API

The MCP server exposes 309 astrology endpoints to Codex CLI as callable tools. Rather than describing an API and hoping the model writes a correct request, it searches the catalogue, reads the real request schema, and makes the call — so the numbers in its answer came from the ephemeris rather than from its training data.

Searching and reading schemas costs nothing. Only a successful call_endpoint spends a credit, and failed calls are free.

Create one in the dashboard. It looks like yt_live_… and carries your credit balance, so treat it as a password: never in client-side code, never committed.

Create an API key

Open ~/.codex/config.toml (Windows: %USERPROFILE%\.codex\config.toml), creating it if it does not exist, and add:

[mcp_servers.occult-api]
command = "npx"
args = ["-y", "occult-api-mcp"]
env = { OCCULT_API_KEY = "yt_live_your_key_here" }

Replace yt_live_your_key_here with your real key. You do not need to install anything else — npx fetches the server on first run.

Ask Codex CLI:

List the tools you have from the occult-api server.

You should get back five tools:

• search_endpoints
• describe_endpoint
• call_endpoint
• get_panchanga
• check_account

If the list is empty the server has not started. The usual cause is the config file being in the right place with the wrong shape, so check the key name above before anything else.

Use the occult-api MCP server to list every endpoint that mentions 'dasha', then call the Vimshottari one for a chart and print the first five mahadashas as a table.

It should call the API rather than answer from memory. If the reply arrives instantly and contains no tool call, the agent has answered from training data — say “use the occult-api tools” and it will.

• Codex configures MCP in TOML, not JSON. The table name carries the server name: `[mcp_servers.occult-api]`.
• Note the underscore in `mcp_servers` — the JSON tools all use camelCase `mcpServers`, and TOML will not correct the spelling for you.
• Codex reads the config at launch. Restart the CLI after editing.

The endpoints are ordinary HTTP. Nothing on this page is required to use them:

curl -X POST https://api.occultapi.com/api/astro/panchanga/ \
  -H 'X-API-Key: yt_live_your_key_here' \
  -H 'Content-Type: application/json' \
  -d '{
    "date_time": "2026-09-17T06:00:00+05:30",
    "latitude": 26.9124,
    "longitude": 75.7873,
    "timezone_as_float": 5.5,
    "keys": ["tithi", "nakshatra", "yogam", "karana"]
  }'

Note the keys array: four calculations in one request, charged as one credit. Calling four times costs four.