
Styx Mcp Server
io.github.timmx7Published by GitHub account timmx7v1.0.0Updated Oct 24, 2026
MCP server for Styx — intelligent AI routing across OpenAI, Anthropic, Google, and Mistral.
Overview
MCP server for a self-hosted Styx AI gateway, letting an assistant route requests across OpenAI, Anthropic, Google and Mistral and manage projects, keys and…
- What you can do
- Send AI requests through the Styx gateway and list available models with pricing
- Set a default model for routing
- List and create projects
- List and create API keys
- Check usage and cost statistics
- Manage BYOK provider keys
- When to use it
- Useful when you run a self-hosted Styx gateway and want an assistant to send model requests through one endpoint, compare models and pricing, or administer projects, API keys and usage from the chat client.
- Requirements
- Runs locally via npx (Node.js 18+); the README also lists Python 3.10+ with mcp, httpx and pydantic. Needs a reachable self-hosted Styx instance; STYX_API_URL and STYX_PROXY_URL default to localhost. STYX_API_KEY is required for sending requests and STYX_TOKEN for management tools.
Installation
In SourceWeft
- Open Styx Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
styx-mcp-server
MCP server for Styx — the intelligent AI gateway that routes requests across OpenAI, Anthropic, Google, and Mistral from a single endpoint.
Connect Claude Code, Cursor, Windsurf, or any MCP-compatible client to your self-hosted Styx instance.
Quick start
Requirements
- Node.js 18+
- Python 3.10+ with dependencies:
Configuration
Set environment variables before starting:
Claude Code config
Add to .claude/mcp.json:
Tools
SSE transport
License
Apache-2.0
Source: styx-mcp-server/README.md at commit 48ddf89
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts