Skip to content

Editor integrations

One MCP server puts 309 astrology endpoints inside whichever coding tool you already use. Pick yours — the setup differs more than it should.

Pick your tool

The part that is the same everywhere

Every one of them runs the same local server over stdio. There is nothing to install first — npx fetches occult-api-mcp on the first run, and your key stays on your machine.

the server definition
{
  "mcpServers": {
    "occult-api": {
      "command": "npx",
      "args": ["-y", "occult-api-mcp"],
      "env": { "OCCULT_API_KEY": "yt_live_your_key_here" }
    }
  }
}

The parts that are not

Four differences account for nearly every failed setup, and none of them produce an error message — the server simply does not appear:

  • VS Code uses a different key. GitHub Copilot reads servers, everything else reads mcpServers.
  • Codex is TOML. Not JSON, and the table is mcp_servers with an underscore.
  • The filename differs. Cursor wants mcp.json; Windsurf and Antigravity want mcp_config.json.
  • Replit has no file at all. It is configured through the Integrations pane.

Each page below carries the exact path and shape for its tool, so you do not have to hold any of this in your head.

Not using an editor agent?

The endpoints are ordinary HTTP with an X-API-Key header, and none of this is required to call them. If you are wiring them into your own LLM application rather than your editor, the function-calling guide covers tool definitions for the major model providers.

Next