MCP servers

We run two MCP servers over Streamable HTTP.

How API tools are charged

An MCP call goes through the same checks as a REST call: the same key, rate limits and credits. Only successful calls on a live key are charged, and a test key is never charged. Arguments are treated like any request body: they are never written to our database or logs.

Start with a test key (al_test_). Keep keys out of files you commit, because a key in an MCP config is a secret key.

Set it up

Claude Code:

claude mcp add --transport http astrologics https://api.astrologics.in/mcp --header "Authorization: Bearer al_test_YOUR_KEY"
claude mcp add --transport http astrologics-docs https://developers.astrologics.in/mcp

Cursor (.cursor/mcp.json):

{ "mcpServers": {
    "astrologics": { "url": "https://api.astrologics.in/mcp", "headers": { "Authorization": "Bearer al_test_YOUR_KEY" } },
    "astrologics-docs": { "url": "https://developers.astrologics.in/mcp" } } }

VS Code (.vscode/mcp.json):

{ "servers": {
    "astrologics": { "type": "http", "url": "https://api.astrologics.in/mcp", "headers": { "Authorization": "Bearer al_test_YOUR_KEY" } },
    "astrologics-docs": { "type": "http", "url": "https://developers.astrologics.in/mcp" } } }

Fewer tools

The API server lists every operation, which is a lot for an agent to hold in mind. To list only some domains, add ?domains= with the slugs from the reference, for example https://api.astrologics.in/mcp?domains=kundli,dasha.

Add ?compact=1 to spend less of the agent's context: tools come with a one-line summary and no field descriptions, and a call answers with data and any warnings, without meta. It works with domains, as in https://api.astrologics.in/mcp?domains=vastu&compact=1.