agent-gateway
Server Details
Relux Works studio gateway: read services/pricing and submit a project inquiry to hire the team.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: one retrieves pricing information, the other submits a project quote request. No functional overlap.
Both tool names follow the consistent verb_noun pattern (get_services_pricing, request_project_quote), making them predictable.
With only two tools, the server feels minimal but may be appropriate for a very narrow scope like a simple inquiry and quote system.
The tools cover the core workflow (view pricing and request a quote), but lack additional capabilities like tracking quote status or managing submissions.
Available Tools
2 toolsget_services_pricingGet services and pricingRead-onlyIdempotentInspect
Returns Relux Works services, fixed-price packages, company facts, selected work, supported languages, and market-specific planning prices. Tool and service identifiers remain in English.
| Name | Required | Description | Default |
|---|---|---|---|
| market | No | Preferred market or ISO country code, for example us, gb, de, ae, sa, sg, il, ca, or au. | |
| preferred_language | No | Preferred BCP 47 language for regional filtering and the agent presentation, for example de, fr, ar, ar-AE, fa, or he. Canonical catalog prose remains in English. |
request_project_quoteRequest a project quoteDestructiveInspect
Creates and immediately sends an external project inquiry to a private Relux Works Telegram chat for human review. Do not call it to test the connector or demonstrate MCP. Build the summary from known conversation context, ask only for missing details, obtain a real user-provided or user-confirmed reply route to the decision maker or an accountable relay agent, and show the complete draft including that route. Before calling, provide https://relux.works/en/privacy-policy/ and obtain explicit user consent. Never invent or infer contact details. The current MCP chat is not a reply route. A human replies within one business day with a recommended package and a fixed-price quote.
| Name | Required | Description | Default |
|---|---|---|---|
| market | No | Client market or country code | |
| summary | Yes | What the user wants to build or fix, current state, goals (required) | |
| timeline | No | Desired timeline or deadline | |
| budget_usd | No | Approximate budget in USD, if known | |
| client_name | No | Name of the person or company | |
| project_type | No | Closest project category | |
| contact_email | No | Real, reachable decision-maker email provided or explicitly confirmed by the user. Never invent or infer it. Legacy shorthand for reply_contact with channel=email and recipient=decision_maker. Reserved example and test domains are rejected. | |
| reply_contact | No | External route provided or explicitly confirmed by the user that a Relux Works human can use to reach the decision maker or a relay agent. Never invent or infer it. The current MCP session, chat, or inquiry ID does not qualify. | |
| consent_confirmed | Yes | Set to true only after the user has reviewed the complete inquiry and reply route, received the privacy notice URL, and explicitly approved submission to Relux Works. | |
| preferred_language | No | Language preferred for the human reply |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!