Skip to main content
Glama

Western Astrology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Compatibility score - Relationship compatibility API

post_astrology_compatibility_score
Read-only

Calculate a detailed compatibility score between two birth charts using Western synastry (inter-chart aspects). Returns overall score (0-100) plus category breakdowns for romantic, emotional, intellectual, physical, and spiritual compatibility. Each category analyzes specific planetary pairs: Venus-Mars for romance, Moon-Moon for emotions, Mercury-Mercury for intellect. Includes Sun, Moon, Venus, and Mars sign compatibility narratives, element balance analysis, relationship archetype classification, and the most significant inter-chart aspects with relationship-specific interpretations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
person1YesFirst person birth details (date, time, location, timezone). Required for calculating natal planetary positions.
person2YesSecond person birth details. Compared against person1 to evaluate inter-chart aspects and compatibility.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
personsYes
summaryYes
archetypeYes
strengthsYes
categoriesYes
challengesYes
keyAspectsYes
overallScoreYes
elementBalanceYes
interpretationYes
aspectBreakdownYes
signCompatibilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / person1 / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time."
    • changedInput schema / properties / person2 / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "archetype": {
+      "properties": {
+        "description": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "label",
+        "description"
+      ],
+      "type": "object"
+    },
+    "aspectBreakdown": {
+      "properties": {
+        "challenging": {
+          "type": "number"
+        },
+        "harmonious": {
+          "type": "number"
+        },
+        "neutral": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total",
+        "harmonious",
+        "challenging",
+        "neutral"
+      ],
+      "type": "object"
+    },
+    "categories": {
+      "properties": {
+        "emotional": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "intellectual": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "physical": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "romantic": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        },
+        "spiritual": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "required": [
+        "romantic",
+        "emotional",
+        "intellectual",
+        "physical",
+        "spiritual"
+      ],
+      "type": "object"
+    },
+    "challenges": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "elementBalance": {
+      "properties": {
+        "description": {
+          "type": "string"
+        },
+        "person1": {
+          "properties": {
+            "air": {
+              "type": "number"
+            },
+            "earth": {
+              "type": "number"
+            },
+            "fire": {
+              "type": "number"
+            },
+            "water": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "fire",
+            "earth",
+            "air",
+            "water"
+          ],
+          "type": "object"
+        },
+        "person2": {
+          "properties": {
+            "air": {
+              "type": "number"
+            },
+            "earth": {
+              "type": "number"
+            },
+            "fire": {
+              "type": "number"
+            },
+            "water": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "fire",
+            "earth",
+            "air",
+            "water"
+          ],
+          "type": "object"
+        },
+        "sharedElement": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "person1",
+        "person2",
+        "sharedElement",
+        "description"
+      ],
+      "type": "object"
+    },
+    "interpretation": {
+      "type": "string"
+    },
+    "keyAspects": {
+      "items": {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "interpretation": {
+            "enum": [
+              "harmonious",
+              "challenging",
+              "neutral"
+            ],
+            "type": "string"
+          },
+          "orb": {
+            "type": "number"
+          },
+          "planet1": {
+            "type": "string"
+          },
+          "planet2": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet1",
+          "planet2",
+          "type",
+          "orb",
+          "interpretation",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "overallScore": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    "persons": {
+      "properties": {
+        "person1": {
+          "properties": {
+            "mars": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            },
+            "moon": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            },
+            "sun": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            },
+            "venus": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            }
+          },
+          "required": [
+            "sun",
+            "moon",
+            "venus",
+            "mars"
+          ],
+          "type": "object"
+        },
+        "person2": {
+          "properties": {
+            "mars": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            },
+            "moon": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            },
+            "sun": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            },
+            "venus": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            }
+          },
+          "required": [
+            "sun",
+            "moon",
+            "venus",
+            "mars"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "person1",
+        "person2"
+      ],
+      "type": "object"
+    },
+    "signCompatibility": {
+      "properties": {
+        "mars": {
+          "properties": {
+            "description": {
+              "type": "string"
+            },
+            "person1Sign": {
+              "type": "string"
+            },
+            "person2Sign": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "person1Sign",
+            "person2Sign",
+            "description"
+          ],
+          "type": "object"
+        },
+        "moon": {
+          "properties": {
+            "description": {
+              "type": "string"
+            },
+            "person1Sign": {
+              "type": "string"
+            },
+            "person2Sign": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "person1Sign",
+            "person2Sign",
+            "description"
+          ],
+          "type": "object"
+        },
+        "sun": {
+          "properties": {
+            "description": {
+              "type": "string"
+            },
+            "person1Sign": {
+              "type": "string"
+            },
+            "person2Sign": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "person1Sign",
+            "person2Sign",
+            "description"
+          ],
+          "type": "object"
+        },
+        "venus": {
+          "properties": {
+            "description": {
+              "type": "string"
+            },
+            "person1Sign": {
+              "type": "string"
+            },
+            "person2Sign": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "person1Sign",
+            "person2Sign",
+            "description"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "sun",
+        "moon",
+        "venus",
+        "mars"
+      ],
+      "type": "object"
+    },
+    "strengths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "overallScore",
+    "categories",
+    "persons",
+    "signCompatibility",
+    "elementBalance",
+    "archetype",
+    "strengths",
+    "challenges",
+    "summary",
+    "interpretation",
+    "aspectBreakdown",
+    "keyAspects"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / person1 / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."
    • changedInput schema / properties / person2 / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."
  4. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]
  5. Changed4 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "person1": {
+      "date": "1990-07-15",
+      "latitude": 40.7128,
+      "longitude": -74.006,
+      "time": "14:30:00",
+      "timezone": -5
+    },
+    "person2": {
+      "date": "1990-07-15",
+      "latitude": 40.7128,
+      "longitude": -74.006,
+      "time": "14:30:00",
+      "timezone": -5
+    }
+  }
+]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
    • changedInput schema / properties / person1 / properties / nodeType / description
      Previous value: -"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\"."New value: +"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\"."
    • changedInput schema / properties / person2 / properties / nodeType / description
      Previous value: -"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\"."New value: +"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\"."
  6. Changed2 schema fields changed
    • addedInput schema / properties / person1 / properties / nodeType
      Added value: +{
+  "default": "true",
+  "description": "Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".",
+  "enum": [
+    "mean",
+    "true"
+  ],
+  "example": "true",
+  "type": "string"
+}
    • addedInput schema / properties / person2 / properties / nodeType
      Added value: +{
+  "default": "true",
+  "description": "Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".",
+  "enum": [
+    "mean",
+    "true"
+  ],
+  "example": "true",
+  "type": "string"
+}
  7. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  8. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}
  9. Changed4 schema fields changed
    • changedInput schema / properties / person1 / properties / timezone / anyOf
      Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / person1 / properties / timezone / description
      Previous value: -"Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\", \"Asia/Kolkata\"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."
    • changedInput schema / properties / person2 / properties / timezone / anyOf
      Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / person2 / properties / timezone / description
      Previous value: -"Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\", \"Asia/Kolkata\"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."
  10. First observed

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is already known. The description adds useful context about the return categories (romantic, emotional, etc.) and specific planetary pairs, but does not disclose any additional behavior such as error handling, rate limits, or edge cases. Since output schema exists, return format details are not required here. The description adds moderate value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one focused paragraph that front-loads the core purpose ('Calculate a detailed compatibility score...') and then enumerates the breakdowns. It is detailed but not bloated, with each sentence contributing useful information about output composition. Slightly longer than necessary but well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with a rich input schema and an output schema (indicated), the description covers the key aspects: what it returns (score, categories, narratives, elements, archetypes, aspects). It does not mention when to choose this over the sibling post_astrology_synastry, which is a notable gap given the tool list. Otherwise, it is complete for the given complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with detailed descriptions for person1, person2, lang, and compact. The tool description itself adds no parameter-specific information beyond what the schema already provides, so it does not elevate the semantics. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it calculates a detailed compatibility score between two birth charts using Western synastry, with specific verb and resource. It lists return contents, but does not explicitly distinguish itself from the sibling post_astrology_synastry, which also likely deals with inter-chart aspects. Thus it is clear but lacks explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this tool versus alternatives like post_astrology_synastry or post_astrology_composite_chart. It does not state when not to use it or mention any prerequisites beyond the required input. The agent must infer its applicability from the name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Western Astrology MCP Server by RoxyAPI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources