Flume Context MCP Server
Flume Health runs a remote Model Context Protocol server at https://console.flumehealth.com/api/v1/context/mcp. It was not found in any directory, registry, docs page, or llms.txt — it was discovered by probing /.well-known/oauth-protected-resource on the Flume Console host, which names the MCP endpoint as its protected resource. The endpoint is live and OAuth-protected: an unauthenticated JSON-RPC POST returns HTTP 401 with `WWW-Authenticate: Bearer resource_metadata="https://console.flumehealth.com/.well-known/oauth-protected-resource"`, which is the RFC 9728 discovery pattern MCP clients follow. The live tool list therefore requires an authenticated introspection and is NOT recorded here. Flume publishes no MCP tool documentation and no llms.txt, so no tool names or inputSchemas exist to fall back on — recording any would be fabrication.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.