Skip to content

Require org-scoped Langfuse key for Cursor and Hermes MCP - #3

Merged
astraltrekkin merged 3 commits into
mainfrom
mcp-org-scoped-connect
Aug 30, 2026
Merged

astraltrekkin merged 3 commits into
mainfrom
mcp-org-scoped-connect

Conversation

@astraltrekkin

Copy link
Copy Markdown
Owner

Summary

  • fusion connect cursor and fusion connect hermes now refuse unless an organization-scoped Langfuse key is on the active target (or LANGFUSE_ORG_PUBLIC_KEY / LANGFUSE_ORG_SECRET_KEY).
  • That pair stays in Fusion config. Editor MCP JSON/YAML still has no secrets.
  • Discover uses GET /api/public/organizations/projects when org keys are present so Fusion MCP can answer org-wide project lists.

Test plan

  • ensureOrgScopedKeys unit test
  • connect refuses without org keys; succeeds with them and writes no pk-lf/sk-lf into Cursor mcp.json
  • Set LANGFUSE_ORG_PUBLIC_KEY + LANGFUSE_ORG_SECRET_KEY, run fusion connect cursor / hermes, restart the client, ask Fusion MCP to list org projects

Cursor and Hermes MCP can only list and govern org projects with that key. It is stored in Fusion config (or LANGFUSE_ORG_*), never written into editor MCP files.
…nect.

If the key is not already saved or in env, a TTY prompt collects it and writes it to Fusion config before installing Cursor or Hermes MCP.
@astraltrekkin
astraltrekkin force-pushed the mcp-org-scoped-connect branch from 3d7f519 to 70fab52 Compare August 30, 2026 05:16
@astraltrekkin
astraltrekkin merged commit 70fab52 into main Aug 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant