Skip to main content
Glama
Flux MCP

Flux MCP

Official
by Flux-Search

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FLUX_API_KEYYesRequired Flux API key. It starts with `user_sk_` (personal) or `org_sk_` (workspace).
FLUX_TIMEOUT_MSNoHow long to wait for an answer, in milliseconds.120000
FLUX_API_BASE_URLNoOnly set this to use a different deployment.https://fluxsearch.io

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
lineageA

Read a document or a web page and return only the passages that answer your questions, with the people, places, organisations and dates written in where a passage needs them (the name behind 'she', an exact date for 'last April'). Send text or a url, and the questions in queries. Each question is a separate pass and is billed as one. Without queries, every passage comes back, which is larger than the input. Use it to turn a long source into grounded context.

searchA

Search the web and get ranked results. Pages Flux reads come back with the passages that answer the query, with people, places, organisations and dates written in. Results it could not read are listed with the reason. Use it to find sources; use lineage to read a specific document or link you already have.

fetchA

Fetch one web page and return it whole as clean markdown, with its title and published date. Use it when you need the full page; use lineage when you only need the parts that answer a question, which is cheaper on long pages.

accountA

Show the Flux account balance, and roughly how many tokens of Lineage input it covers. Free. Check it before a large job.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation4/5

The tools have mostly distinct purposes: account checks billing, search finds sources, fetch returns a full page, and lineage extracts targeted passages. The main overlap is between fetch, lineage, and search because all can return web content, but the descriptions explicitly clarify when to use each.

Naming Consistency4/5

All names are single lowercase words, which gives a consistent surface style. However, the set mixes nouns (account, lineage) with verbs (fetch, search), so it is readable but not a strict verb_noun convention.

Tool Count5/5

Four tools is well-scoped for this server: billing, search, full-page retrieval, and grounded extraction. Each tool has a clear role and earns its place without bloat.

Completeness4/5

The core workflow is covered: check balance, search the web, fetch a page, and extract answers from a document or URL. Minor gaps exist around batch reading or managing multiple sources, but agents can work around them by making repeated calls.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues