Skip to main content
GEOMETRY builder support is self-serve by design. Most questions already have an answer in these docs or the install walkthrough. Open a GitHub Issue only when something looks like a product or connectivity bug you can reproduce — not when two zodiac systems disagree.

​
Help yourself first

Use your browser’s search on this site, or paste a docs page into your own agent (Claude / ChatGPT / Cursor) with GEOMETRY MCP connected — that is often faster than waiting on a ticket.

​
Support by plan

This matches common SaaS practice: free tiers get documentation and community-style self-serve; ticketed human support is for paying customers. There is no public support email. GitHub cannot block Issue creation by plan on a public repo. Policy: Issues from non-paying use are closed with a pointer back here. Prove paid by stating your Developer Portal account email (the one on the Stripe / portal subscription) — never paste a zpka_ key.

​
When paid users may open a GitHub Issue

Use Issues for product / connectivity failures, for example:
  • HTTP 5xx, timeouts, empty or truncated responses
  • Client cannot complete the MCP handshake after following Quickstart
  • A tool throws or returns malformed JSON (missing required keys, not “I expected a different sign”)
Do not open Issues for zodiac / calendar disagreements — read Astro wheels and When it covers → Calendar boundaries first. Different systems are supposed to diverge. Open an issue (paid only): github.com/goqolabs/geometry-mcp/issues — title it clearly (e.g. Bug: mcp.geometry.app returns 502 on get_date) and include your portal account email in the body.

​
Do not open Issues for

​
Make a bug report worth filing

Incomplete reports get closed or delayed. Include: Those _no fields are opaque ids — not a public API contract (see Field glossary) — but quoting them helps reproduce a broken payload shape.

​
Leaked key

Roll the key yourself in the Developer Portal, then update your connector URL. The old key stays valid for 7 days (Zuplo grace) — normal vendor behavior. Full steps: Where your key goes → If your key was exposed.

​
Tips

  • One Issue per bug.
  • Paid portal subscription required for Issue handling.
  • Link the docs page you were on if it helps.
  • A free GitHub account is required to open Issues (anyone can click “New”; only paid are in scope).
Quickstart · Astro wheels · Where your key goes · Billing · FAQ