Koskamo

Astrodai MCP

An official streamable HTTP MCP server providing ephemeris-backed astronomical positions, birth-time sensitivity bounds, Panchanga calculations, and Vimshottari dasha transitions for Vedic astrology analysis.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Astrodai MCP logo, by AstrodaiCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by Astrodai
MCP endpoint (Streamable HTTP)
https://astrodai.com/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

6 of 6 have a description · 6 of 6 declare behavior hints · 6 of 6 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve ephemeris-backed astronomical positions
  • Calculate Panchanga and Vimshottari dasha transitions
  • Analyze birth-time sensitivity bounds
  • Integrate with Claude Code CLI or Cursor

Source and maintenance

Community listingRegistry 1.0.0
Maintenance checked

Protocol and capabilities

Server
astrodai 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
6 advertised
Resources
2 advertised
Resource templates
0 advertised
Prompts
3 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Astrodai calculates sidereal (Vedic) birth charts: True Chitrapaksha ayanamsa, whole-sign houses, Vimshottari life chapters (mahadasha and antardasha). Start with find_birthplace to get a place_token, then pass it with the birth date and local birth time (as recorded) to the other tools. The UTC offset is worked out from the place and date. chart_overview: a short plain summary of the rising sign, Moon, Sun and the running life chapter. life_area: plain findings for one area of life. current_chapter: the running life chapter and sub-chapter and the areas they touch. birth_time_check: how many minutes of birth time would change the rising sign. panchang: weekday, tithi, paksha, nakshatra, yoga and karana for a date and place. Results are calculations from the details given. Health is not interpreted. chart_overview, life_area and current_chapter share up to 3 answers per chart every 6 hours; birth_time_check, panchang and find_birthplace have per-connection rate limits only. Birth details are used only to calculate this answer; a one-way code is kept for 6 hours to apply fair-use limits. If the user has attached an Astrodai file, it holds the complete calculation; prefer it for timing questions.

Tools

6 advertised

find_birthplace — Find birthplace
Advertised by the server during the last successful anonymous check.
Advertised read-only

Look up a town in the Astrodai atlas (towns above about 15,000 people; places at or beyond 66 degrees latitude are not supported). Returns up to 5 candidates, each with a place_token for the other tools. Add the region or country after a comma to narrow the search. If nothing matches, try the nearest larger town.

find_birthplace input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "place"
  ],
  "properties": {
    "place": {
      "type": "string",
      "description": "Town name, optionally followed by a comma and the region or country."
    }
  }
}
find_birthplace annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
chart_overview — Birth chart overview
Advertised by the server during the last successful anonymous check.
Advertised read-only

A short plain-language summary of the sidereal birth chart (True Chitrapaksha ayanamsa): the rising sign, the Moon sign and nakshatra and the Sun sign, each with a one-line meaning, and the running Vimshottari life chapter and sub-chapter (month and year). Up to 3 answers per chart every 6 hours, shared with life_area and current_chapter. Birth details are used only to calculate this answer; a one-way code is kept for 6 hours to apply fair-use limits.

chart_overview input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "birth_date",
    "birth_time",
    "place_token"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Birth date, YYYY-MM-DD (1900 to 2099)."
    },
    "birth_time": {
      "type": "string",
      "description": "Local birth time as recorded, 24-hour HH:MM or HH:MM:SS."
    },
    "place_token": {
      "type": "string",
      "description": "place_token from find_birthplace (valid 24 hours)."
    }
  }
}
chart_overview annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
life_area — Life area evidence
Advertised by the server during the last successful anonymous check.
Advertised read-only

Plain-language findings from the birth chart for one area of life: how strong the area's main house is, the planet that guides it and where it sits, the other houses and planets for the area, support from planets (strong, mixed or needs effort), and whether the running life chapter touches the area. Areas: career, relationships, wealth, home_property, children, education, foreign_settlement, spiritual_growth. Health is not covered. Up to 3 answers per chart every 6 hours, shared with chart_overview and current_chapter. Birth details are used only to calculate this answer; a one-way code is kept for 6 hours to apply fair-use limits.

life_area input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "birth_date",
    "birth_time",
    "place_token",
    "area"
  ],
  "properties": {
    "area": {
      "type": "string",
      "description": "One of: career, relationships, wealth, home_property, children, education, foreign_settlement, spiritual_growth."
    },
    "birth_date": {
      "type": "string",
      "description": "Birth date, YYYY-MM-DD (1900 to 2099)."
    },
    "birth_time": {
      "type": "string",
      "description": "Local birth time as recorded, 24-hour HH:MM or HH:MM:SS."
    },
    "place_token": {
      "type": "string",
      "description": "place_token from find_birthplace (valid 24 hours)."
    }
  }
}
life_area annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
current_chapter — Current life chapter
Advertised by the server during the last successful anonymous check.
Advertised read-only

The Vimshottari life chapter (mahadasha) and sub-chapter (antardasha) running today, with month and year, in plain language: what their planets stand for, the houses they sit in and guide, the life areas they touch, and when the next sub-chapter starts. Finer periods are not included. Up to 3 answers per chart every 6 hours, shared with chart_overview and life_area. Birth details are used only to calculate this answer; a one-way code is kept for 6 hours to apply fair-use limits.

current_chapter input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "birth_date",
    "birth_time",
    "place_token"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Birth date, YYYY-MM-DD (1900 to 2099)."
    },
    "birth_time": {
      "type": "string",
      "description": "Local birth time as recorded, 24-hour HH:MM or HH:MM:SS."
    },
    "place_token": {
      "type": "string",
      "description": "place_token from find_birthplace (valid 24 hours)."
    }
  }
}
current_chapter annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
birth_time_check — Birth time sensitivity
Advertised by the server during the last successful anonymous check.
Advertised read-only

How sensitive the chart is to the recorded birth time, in plain language: minutes earlier or later until the rising sign changes, the same for the Moon nakshatra quarter (pada) and the D9 and D10 rising signs, and how many days the life chapter dates move per minute of birth time. It does not correct the birth time. Birth details are used only to calculate this answer and are not stored.

birth_time_check input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "birth_date",
    "birth_time",
    "place_token"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Birth date, YYYY-MM-DD (1900 to 2099)."
    },
    "birth_time": {
      "type": "string",
      "description": "Local birth time as recorded, 24-hour HH:MM or HH:MM:SS."
    },
    "place_token": {
      "type": "string",
      "description": "place_token from find_birthplace (valid 24 hours)."
    }
  }
}
birth_time_check annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
panchang — Panchang for a day
Advertised by the server during the last successful anonymous check.
Advertised read-only

Weekday, tithi, paksha, nakshatra, yoga and karana for a date and place, calculated at 12:00 local time unless a time is given. Sunrise, sunset and Rahu kalam are not included. Birth details are used only to calculate this answer and are not stored.

panchang input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "place_token"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Date, YYYY-MM-DD (1900 to 2099)."
    },
    "time": {
      "type": "string",
      "description": "Local time, 24-hour HH:MM; default 12:00."
    },
    "place_token": {
      "type": "string",
      "description": "place_token from find_birthplace (valid 24 hours)."
    }
  }
}
panchang annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

3 advertised

interpret_chart — Interpret Vedic birth chart

Advertised by the server during the last successful anonymous check.

Structured guide for calculating and interpreting a Vedic birth chart.

birth_date
Birth date, YYYY-MM-DD. (required)
birth_time
Local birth time, 24-hour HH:MM. (required)
birth_place
Town and country of birth. (required)
focus_area
Optional life area focus: career, relationships, wealth, home_property, children, education, foreign_settlement, spiritual_growth.
check_birth_sensitivity — Check birth time sensitivity

Advertised by the server during the last successful anonymous check.

Evaluate if slight inaccuracies in recorded birth time alter the rising sign or lunar nakshatra.

birth_date
Birth date, YYYY-MM-DD. (required)
birth_time
Local birth time, 24-hour HH:MM. (required)
birth_place
Town and country of birth. (required)
daily_panchang — Calculate daily Vedic panchang

Advertised by the server during the last successful anonymous check.

Calculate the five astronomical limbs of the Vedic calendar for a date and location.

date
Date, YYYY-MM-DD. (required)
place
Town and country. (required)

Resources

2 advertised

principles

Advertised by the server during the last successful anonymous check.

Astrodai mathematical calculation standards and astronomical basis.

principles URI
astrodai://principles

MIME type: text/markdown

ethics

Advertised by the server during the last successful anonymous check.

Astrodai ethical guidelines and boundaries for automated chart interpretation.

ethics URI
astrodai://ethics

MIME type: text/markdown

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
764 ms
95th percentile latency
764 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 764 ms · metadata changed · 6 tool(s), 2 resource(s), 0 resource template(s), 3 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http astrodai-mcp https://astrodai.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add astrodai-mcp --url https://astrodai.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable astrodai-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "astrodai-mcp": {
      "url": "https://astrodai.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "astrodai-mcp": {
      "type": "streamableHttp",
      "url": "https://astrodai.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start astrodai-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "astrodai-mcp": {
      "type": "http",
      "url": "https://astrodai.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http astrodai-mcp https://astrodai.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://astrodai.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "astrodai-mcp": {
      "serverUrl": "https://astrodai.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Astrodai MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.