Geometry MCP server
{
"mcpServers": {
"geometry": {
"type": "http",
"url": "https://mcp.geometry.app/mcp?key=YOUR_KEY"
}
}
}{
"mcpServers": {
"geometry": {
"type": "http",
"url": "https://mcp.geometry.app/mcp?key=YOUR_KEY"
}
}
}{
"mcpServers": {
"geometry": {
"type": "http",
"url": "https://mcp.geometry.app/mcp?key=YOUR_KEY"
}
}
}{
"servers": {
"geometry": {
"type": "http",
"url": "https://mcp.geometry.app/mcp?key=YOUR_KEY"
}
}
}{
"mcpServers": {
"geometry": {
"type": "http",
"url": "https://mcp.geometry.app/mcp?key=YOUR_KEY"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.66.0
What it does
Geometry exposes deterministic temporal and symbolic data for AI agents via three tools: date identity resolution, date compatibility comparison, and name-to-cosmic-card mapping. It covers the Gregorian calendar from 1900–2100 and returns the same JSON bytes for the same input every time, with no hallucination or external dependencies.
- Resolve a birth date to its associated calendars, seasons, moon phases, and symbolic card identity.
- Compare two dates to find shared symbolic systems and compatibility across cosmic reference systems.
- Map a person's name to cosmic cards and compute ~100 Latin cipher sums for symbolic analysis.
Tools this server exposes
| Tool | Does |
|---|---|
| get_date | Resolve one civil date to stable calendars, seasons, moon phases, planetary retrogrades, and card identity. |
| get_compatibility | Compare two dates across shared symbolic systems and return compatibility metrics. |
| get_name | Map a name to cosmic cards and compute ~100 Latin cipher sums. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.