From octave
Displays current Octave MCP server connection status including workspace and organization. Use for 'which workspace', 'show connection', 'what server', or Octave setup queries.
npx claudepluginhub octavehq/lfgtm --plugin octaveThis skill uses the workspace's default tool permissions.
Show which Octave MCP server is connected.
Manages Model Context Protocol (MCP) servers for Claude Code projects: installs/configures .mcp.json, OAuth remotes, runtime enable/disable, troubleshooting connections.
Diagnoses and resolves MCP server connection issues for Claude Code (WSL) and Claude Desktop (Windows). Tests mcptools (R), Hugging Face MCP (mcp-remote); handles auth failures, transport errors, setup.
List tools and invoke calls on MCP servers using fastmcp CLI. Handles HTTP/Python files/configs/stdio targets, schemas, JSON output, auth, and discovery for workflows.
Share bugs, ideas, or general feedback.
Show which Octave MCP server is connected.
Find the Octave MCP server by looking at your available tools for ones like verify_connection, get_entity, list_all_entities.
Call verify_connection to confirm the API key is valid and to fetch the authoritative workspace/organization names. This is the canonical probe.
Show the server name and workspace info from the verify_connection response:
Current Octave Workspace
========================
MCP Server: <mcpServerName>
Workspace: <workspaceName> (<workspaceOId>)
Organization: <organizationSlug> (<organizationOId>)
No Octave MCP server detected.
Add one with: claude mcp add octave-<workspaceName> --transport http <url>
If verify_connection fails (invalid API key, network error): surface the error message and suggest re-running claude mcp add with a fresh API key.
If user asks to switch: Explain they need to configure a different MCP server in their Claude settings.