Back to Browse

Auxen MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Provision private AI model endpoints on dedicated GPUs (Llama, Qwen, Mistral). Pay per minute.

About

Provision private AI model endpoints on dedicated GPUs (Llama, Qwen, Mistral). Pay per minute.

Remote endpoints: streamable-http: https://api.auxen.ai/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "ai-auxen-auxen": {
      "url": "https://api.auxen.ai/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Auxen MCP Server

This is the public manifest repo for the Auxen MCP (Model Context Protocol) server. The server itself runs at https://api.auxen.ai/mcp — this repo exists so registries (Smithery, Glama, the official MCP registry) have a canonical place to read metadata from.

Connect

The Auxen MCP server is a remote, StreamableHTTP server. Add it to your MCP client by URL:

https://api.auxen.ai/mcp

Authentication uses OAuth 2.1 + PKCE (recommended for browser-based clients) or a direct Auxen API key (auxen_live_* / auxen_test_*) sent as Authorization: Bearer <key>.

OAuth flow

The discovery metadata is at:

  • https://api.auxen.ai/.well-known/oauth-authorization-server (RFC 8414)
  • https://api.auxen.ai/.well-known/oauth-protected-resource (RFC 9728)

Clients that support Dynamic Client Registration (RFC 7591) — including Claude.ai's Connectors Directory — can register themselves automatically. After registration the client redirects the user's browser to https://api.auxen.ai/oauth/authorize, the user logs in to Auxen and approves the connection on https://auxen.ai/oauth/authorize, and the client receives an authorization code that exchanges for an access token at https://api.auxen.ai/oauth/token.

Direct key (programmatic)

For agents that don't go through a browser, generate an auxen_live_* (or auxen_test_*) key at https://auxen.ai/dashboard/api-keys and send it as Authorization: Bearer <key> on every MCP call.

Tools

ToolEffectHint
auxen_list_modelsList available models, optionally filtered by sizeread-only
auxen_get_instance_statusGet status, endpoint, api_key for an instanceread-only
auxen_list_instancesList all instances on the accountread-only
auxen_get_balanceRead USD credits + active subscriptionsread-only
auxen_provision_modelProvision a new model instance — spends moneydestructive
auxen_destroy_instanceDestroy an instance — irreversibledestructive

What is Auxen?

Auxen provisions private, dedicated GPU instances running open-source models (Llama 3.1, Qwen 2.5, Mistral, Gemma 2, Phi-3). Each instance is fully private — no shared inference, no third-party routing. Pay-per-minute billing, no subscriptions.

For the human-facing documentation:

Support

Reviews

No reviews yet

Be the first to review this server!

Auxen MCP Server - Provision private AI model endpoints on dedicated GPUs | MCP Marketplace