Stats
Actions
Tags
From octave
Shows current Octave MCP server connection and workspace status. Useful for verifying which workspace is active and troubleshooting connection issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/octave:workspaceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Show which Octave MCP server is connected.
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.
npx claudepluginhub octavehq/lfgtm --plugin octaveDiagnoses and fixes MCP server connection issues between Claude Code, Claude Desktop, and MCP servers. Covers Windows argument parsing, authentication failures, transport issues, and platform-specific debugging.
Detects MCPProxy connection by checking for mcp__MCPProxy__* tools, suggests /mcp reconnect if missing, and guides MCP tools usage over HTTP API for debugging.
Manages Model Context Protocol (MCP) servers for Claude Code projects: installs/configures .mcp.json, OAuth remotes, runtime enable/disable, troubleshooting connections.