Stellara
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@StellaraSearch the web for recent AI news and save the top results to memory."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Stellara
Stellara is a self-hosted AI tool gateway for Firecrawl, Exa, Qdrant, and an embeddings backend. It exposes one token-protected HTTP and Model Context Protocol (MCP) interface for LLM clients such as Claude Desktop and ChatGPT connectors.
The gateway centralizes upstream credentials, authentication, rate limits, response validation, and network safeguards. It also provides Playwright browser sessions, per-user vector memory, and domain availability checks.
Capabilities
web_*— search, scrape, crawl, extract, and make guarded HTTP or GraphQL requests.browser_*— run interactive Playwright sessions for navigation, forms, screenshots, PDFs, and JavaScript evaluation.memory_*— store and retrieve per-user context through embeddings and Qdrant.domain_availability— check domain registration through RDAP with a WHOIS fallback.OAuth 2.1 and MCP — connect token-based clients or OAuth-capable MCP clients through one gateway.
See the tool reference for the complete catalog.
Related MCP server: mcp-firecrawl
Requirements
Node.js 24 or newer
pnpm 10.33.4 through Corepack
Provider credentials for the features you enable
Docker for the container deployment
Local development
corepack enable
pnpm install
cp .env.example .envSet a public base URL, at least one STELLARA_TOKEN_<USERID>, and the required Firecrawl values in .env. Optional Exa, Qdrant, and embeddings credentials enable their matching tool families.
See the runtime configuration reference for every key, its default, dependencies, and restart behavior.
Start the development server:
pnpm devThe health endpoint is available at http://localhost:8787/health unless PORT is changed.
Container deployment
To deploy on a new host, you need Docker Engine with the Compose plugin, a separately running Firecrawl service, a TLS reverse proxy, and a public HTTPS URL. Stellara uses two existing external Docker networks: internal to reach Firecrawl and the network named by STELLARA_PROXY_NETWORK shared with the proxy. Prepare .env with FIRECRAWL_BASE_URL, FIRECRAWL_API_KEY, PUBLIC_BASE_URL, STELLARA_PROXY_NETWORK, and at least one strong STELLARA_TOKEN_<USERID>; the persistent stellara-data/ directory must belong to UID/GID 999.
Compose selects its image through STELLARA_IMAGE. Pin a release tag or digest for production: the current default, ghcr.io/sebastian-software/stellara:0.1.15, is available only for linux/amd64 and predates the #11 token-snapshot changes. To run this checkout or use an ARM64 host, build from docker/Dockerfile and set STELLARA_IMAGE=stellara:local. The latest tag moves and does not identify a reproducible release.
Follow the operations guide for network attachment, a secret-safe Compose preflight, first boot, health checks, and backup and restore before exposing the service.
Development and tests
The required local quality gate is:
pnpm agent:checkThis command runs type checking, linting, formatting verification, and the hermetic unit suite. Live provider tests are optional, local-only, and require credentials supplied through normal environment variables:
pnpm test:integrationGitHub Actions never receives or runs these integration credentials.
Documentation
Some in-depth documentation is currently available in German. Translation work is tracked in the public issue tracker.
Contributing and support
Read CONTRIBUTING.md before opening a pull request. Use GitHub Issues for reproducible bugs and focused feature proposals. See SUPPORT.md for the project support policy.
Report security vulnerabilities privately as described in SECURITY.md. Do not disclose vulnerabilities in public issues.
License
Stellara is available under the MIT License. The project currently adopts no separate naming or trademark policy.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for Firecrawl — web search, scraping, and biomedical/arXiv paper search.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Related MCP Servers
- FlicenseCqualityCmaintenanceBuilt as a Model Context Protocol (MCP) server that provides advanced web search, content extraction, web crawling, and scraping capabilities using the Firecrawl API.41-
- AlicenseNot gradedqualityBmaintenanceWeb scraping and search MCP server that wraps Firecrawl API for URL discovery and web search with optional content retrieval.140 npm1MIT
- AlicenseNot gradedqualityCmaintenanceA security-first, bring-your-own-key MCP server for bounded Firecrawl scraping, search, site mapping, credit visibility, and queue status.1MIT
- AlicenseNot gradedqualityCmaintenanceExposes remote, agent-facing MCP endpoints over Streamable HTTP for web search, webpage parsing, local knowledge-base retrieval and document creation, and delegation of tasks to configurable LLM providers. Also bundles an admin console with onboarding, provider/model configuration, API-key management, and call logging.MIT