← Registry

Developer Tools

relux.works

Provides pricing and project inquiry submission for an agency offering AI MVP development, app publishing, and related services.

1 endpoint2 known toolsFirst detected July 12, 2026Last detected August 29, 2026

ENDPOINT 1

https://api.relux.works/mcp

No auth detected

MCP server metadata

Name
relux-works-agent-gateway
Version
1.3.0
Capabilities
tools
Server instructions

Agent gateway for Relux Works, an AI-native software development studio. Use get_services_pricing when the user asks specifically about Relux Works services, examples, or regional planning budgets. Use request_project_quote only when the user explicitly wants to contact Relux Works. Turn the known conversation context into a concise inquiry covering the current state, desired outcome, constraints, platform, budget, and timeline. Ask only for missing required or decision-relevant details. Obtain a real reply contact for either the decision maker or an accountable relay agent that can receive and pass on the response. The contact must be provided or explicitly confirmed by the user; never invent, infer, or substitute one. The current MCP session, chat, or inquiry ID is not a reply channel. Tell the user that an accepted inquiry is delivered to a private Relux Works Telegram chat and provide https://relux.works/en/privacy-policy/. Show the complete draft and reply route, then obtain explicit consent before calling request_project_quote. Set consent_confirmed to true only after that approval. Never submit autonomously or call the write tool for tests, probes, examples, or demonstrations. A human replies through the provided contact within one business day. Canonical facts: https://relux.works/llms.txt

Known tools 2

get_services_pricing

Returns Relux Works services, fixed-price packages, company facts, selected work, supported languages, and market-specific planning prices.

Inferred read-only
request_project_quote

Creates and immediately sends an external project inquiry to a private Relux Works Telegram chat for human review.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.relux-works-agent-gateway]
url = "https://api.relux.works/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "relux-works-agent-gateway": {
      "type": "http",
      "url": "https://api.relux.works/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: relux-works-agent-gateway
Remote MCP URL: https://api.relux.works/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "relux-works-agent-gateway": {
      "url": "https://api.relux.works/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "relux-works-agent-gateway": {
      "type": "http",
      "url": "https://api.relux.works/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "relux-works-agent-gateway",
  "transport": "streamable-http",
  "url": "https://api.relux.works/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for relux.works was fetched 2026-09-15T21:54:18.118Z.

Trust status Neutral

relux.works is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.