Switch between local and remote DanNet servers on the fly. This tool allows you to change the DanNet server endpoint during runtime without restarting the MCP server. Useful for switching between development (local) and production (remote) servers. Args: server: Server to switch to. Options: - "local": Use localhost:3456 (development server) - "remote": Use wordnet.dk (production server) - Custom URL: Any valid URL starting with http:// or https:// Returns: Dict with status information: - status: "success" or "error" - message: Description of the operation - previous_url: The URL that was previously active - current_url: The URL that is now active Example: # Switch to local development server result = switch_dannet_server("local") # Switch to production server result = switch_dannet_server("remote") # Switch to custom server result = switch_dannet_server("https://my-custom-dannet.example.com")

Get information about the currently active DanNet server. Returns: Dict with current server information: - server_url: The base URL of the current DanNet server - server_type: "local", "remote", or "custom" - status: Connection status information Example: info = get_current_dannet_server() # Returns: {"server_url": "https://wordnet.dk", "server_type": "remote", "status": "active"}

List issues in the user's Linear workspace. For my issues, use "me" as the assignee. Use "null" for no assignee.

Add a remote MCP server or REST API to your workspace.

Validate an oh-my-posh configuration against the schema. Supports JSON, YAML, and TOML formats.

Search for grouped issues/problems in Sentry - returns a LIST of issues, NOT counts or aggregations. Uses AI to translate natural language queries into Sentry issue search syntax. Returns grouped issues with metadata like title, status, and user count. USE THIS TOOL WHEN USERS WANT: - A LIST of issues: 'show me issues', 'what problems do we have' - Filtered issue lists: 'unresolved issues', 'critical bugs' - Issues by impact: 'errors affecting more than 100 users' - Issues by assignment: 'issues assigned to me' - User feedback: 'show me user feedback', 'feedback from last week' DO NOT USE FOR COUNTS/AGGREGATIONS: - 'how many errors' → use search_events - 'count of issues' → use search_events - 'total number of errors today' → use search_events - 'sum/average/statistics' → use search_events ALSO DO NOT USE FOR: - Individual error events with timestamps → use search_events - Details about a specific issue ID or Sentry issue URL → use get_sentry_resource REMEMBER: This tool returns a LIST of issues, not counts or statistics! <examples> search_issues(organizationSlug='my-org', naturalLanguageQuery='critical bugs from last week') search_issues(organizationSlug='my-org', naturalLanguageQuery='unhandled errors affecting 100+ users') search_issues(organizationSlug='my-org', naturalLanguageQuery='issues assigned to me') search_issues(organizationSlug='my-org', naturalLanguageQuery='user feedback from production') </examples> <hints> - If the user passes a parameter in the form of name/otherName, it's likely in the format of <organizationSlug>/<projectSlugOrId>. - Parse org/project notation directly without calling find_organizations or find_projects. - The projectSlugOrId parameter accepts both project slugs (e.g., 'my-project') and numeric IDs (e.g., '123456'). </hints>