Qortex

io.github.BijikyuPublished by GitHub account Bijikyuv1.0.0Updated Oct 29, 2026

Call AI by role, not by model: tiered AI gateway over REST and MCP.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Qortex is a remote AI gateway that lets an assistant call AI by role rather than by model name, over REST and MCP.

What you can do
  • Route AI requests by role instead of choosing a specific model.
  • Use the gateway over MCP from a connected assistant, or over REST from other clients.
  • Rely on tiered routing to pick the model behind each role.
  • Authenticate with Forgewise SSO or an API key header.
When to use it
Useful when you want an assistant to reach AI models through a role-based, tiered gateway instead of wiring up individual model providers, and when a hosted remote endpoint fits your setup better than a local server.
Requirements
A remote MCP endpoint at qortex.forgewise.tech over streamable HTTP. Authentication is required: Forgewise SSO, or an x-api-key header as an alternative. An API key can be obtained from the provider's keys page. Network access to the endpoint is needed.
Before you install
You must supply credentials: either Forgewise SSO or an x-api-key secret. Requests and prompts are sent to a third-party hosted gateway, so consider what data leaves your machine. The manifest lists no tools, so the exact capabilities and any usage costs are not documented here.

Installation

In SourceWeft

  1. Open Qortex in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Bijikyu%2Fqortex/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "qortex": {
      "type": "http",
      "url": "https://qortex.forgewise.tech/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.