Add Elasticflow MCP server to catalog

[masher00909]

Summary

Adds Elasticflow to the ToolHive catalog as a remote MCP server (Streamable HTTP + OAuth 2.1).

• Name: io.github.stacklok/elasticflow
• Title: Elasticflow
• Remote URL: https://mcp.elasticflow.app/mcp
• Transport: streamable-http
• Auth: OAuth 2.1 with PKCE (no API keys)
• Tier: Community
• Status: Active
• License: MIT
• Tools: 46 across 5 surfaces (workspaces, tables, documents, files, interfaces)

What Elasticflow is

Elasticflow is an AI-native workspace for business — a single place where AI agents and the team work together on structured data, documents, files, and live dashboards. The MCP server exposes that workspace so any MCP-compatible client (Claude, ChatGPT, Cursor, Cline, Copilot Studio, Amazon Q, Gemini, and others) can read business data, produce durable artifacts, and publish results the whole organization sees.

The server is already listed in the Official MCP Registry as app.elasticflow/mcp (v1.0.0).

Files added

• registries/toolhive/servers/elasticflow/server.json — catalog entry following the upstream MCP ServerJSON schema with ToolHive _meta extensions (tier, status, tags, tools, custom_metadata)
• registries/toolhive/servers/elasticflow/icon.svg — logo

Checklist

• server.json uses the upstream MCP schema (2025-12-11)
• _meta.io.modelcontextprotocol.registry/publisher-provided.io.github.stacklok extension key matches remotes[0].url
• JSON is valid
• Folder name is lowercase-hyphenated
• Icon is provided alongside server.json
• Server is public (no auth required to reach — OAuth kicks in on first tool call)

Links

• Website: https://www.elasticflow.app
• GitHub: https://github.com/elasticflowapp/elasticflow-mcp
• Sign-up: https://p.elasticflow.app/signup-earlybirds
• Official MCP Registry listing: https://registry.modelcontextprotocol.io/v0.1/servers/app.elasticflow%2Fmcp/versions/1.0.0

[JAORMX]

Thanks for the submission — this is the most complete of the recent remote-server PRs: https://mcp.elasticflow.app/mcp is a real OAuth 2.1 MCP endpoint (unauthenticated initialize returns 401, and .well-known/oauth-protected-resource resolves), the namespace/location/tier/_meta key are all correct, it's MIT, and you actually committed an icon.svg. A few changes before it can go in:

Please fix:

1. Overview format. The overview must start with a ## Elasticflow heading followed by ~3–5 sentences. The current value is marketing copy (opens with "One workspace where…" and includes a bulleted feature list, no heading). Please reformat to ## Elasticflow\n\n + a concise 3–5 sentence description.
2. Add the repository field. The top-level repository is missing. Add:

   "repository": { "url": "https://github.com/elasticflowapp/elasticflow-mcp", "source": "github" }

3. Icon src host. It points to raw.githubusercontent.com/stacklok/toolhive-catalog/..., but every existing entry references stacklok/toolhive-registry (https://raw.githubusercontent.com/stacklok/toolhive-registry/main/registries/toolhive/servers/elasticflow/icon.svg). Please match that host so it's consistent with the rest of the catalog (the committed icon.svg itself is fine). If the canonical host has intentionally changed, a maintainer can confirm.
4. Remove metadata.last_updated. That field is auto-populated by CI and shouldn't be set by hand.

Minor / confirm:

• OAuth looks correct via discovery (.well-known/oauth-protected-resource), so no explicit oauth_config is needed — consistent with other OAuth remotes like atlassian-remote. tags already include oauth. 👍
• One note: being listed in the upstream Official MCP Registry isn't part of our inclusion criteria — we evaluate each entry independently against our criteria. Not a blocker, just clarifying.

Happy to re-review once the overview, repository, icon host, and metadata are addressed.