MCP

Connect an AI agent to Talismos

Talismos runs an MCP (Model Context Protocol) server — a live connection any MCP-compatible AI agent (Claude, n8n, and others) can use to call the real chart engine directly, inside a conversation.

What this actually is

This isn't a prompt or a set of instructions you paste into a chat. It's a real server your AI client connects to over HTTP: it authenticates once with your API key, then the client itself discovers and calls the available tools — the model decides when to use them, but the calculation always runs on Talismos's real engine, not a guess.

Authentication — two ways, pick whichever your client supports

Automatic (OAuth) — Claude.ai, Claude Desktop

These clients handle login for you: paste the server URL, sign in to Talismos when prompted, approve the connection, and an API key is created and wired in automatically. Nothing to copy or paste.

Manual (API key) — n8n and anything else

Generate an API key from your dashboard and set it as a Bearer token yourself (the same key you'd use for the REST API). Every tool call counts against that account's plan quota exactly like a direct API call would, regardless of which path you used to connect.

Need an API key? Create a free account to generate one. Create free account

How to connect

Claude Desktop

  1. Open Settings → Connectors.
  2. Click Add → "Add custom connector".
  3. Paste the server URL above and click Add.
  4. Sign in to Talismos and approve the connection when prompted — no API key needed.

Claude.ai (web)

  1. Open Settings → Connectors.
  2. Click Add → "Add custom connector".
  3. Paste the server URL above and click Add.
  4. Sign in to Talismos and approve the connection — Claude.ai handles the rest automatically.

n8n

  1. Generate an API key from your Talismos dashboard first.
  2. Add an "MCP Client" node to your workflow.
  3. Set its Server URL to the address above.
  4. Set the Authorization header to "Bearer" followed by your API key.

Available tools

Both tools require an exact birth date, time, and location — the connected agent will ask for anything missing rather than guess.

calculate_birth_chart

Full natal chart, same data as POST /v1/birth-chart.

Input: Birth date, time, latitude/longitude, plus optional house system, zodiac, and language.

Output: Planets, points, angles, houses, and aspects as structured JSON.

get_chart_context

The same chart formatted for conversation, same data as POST /v1/chart-context.

Input: Same fields as calculate_birth_chart.

Output: The chart as prose and markdown, ready to use directly as context in the conversation.

Try saying this

Once connected, you can just ask in plain language — the agent will ask you for anything it's missing (exact birth date, time, and location) before calculating.

“Calculate my birth chart — I was born October 10, 1995, at 2:30 PM in Florianópolis, Brazil.”

“What's my Sun sign and Ascendant?”

“Give me my chart as something you can use as context for the rest of this conversation.”