Himalayas Remote Jobs MCP Server

Created By
Himalayas-Appa year ago
A Model Context Protocol (MCP) server that provides access to remote job listings and company information from Himalayas.app.
Overview

What is Himalayas Remote Jobs MCP Server?

Himalayas Remote Jobs MCP Server is a Model Context Protocol (MCP) server that provides access to remote job listings and company information from Himalayas.app.

How to use Himalayas Remote Jobs MCP Server?

To use the server, connect to the public MCP server URL and utilize the available job and company search tools through your AI coding assistant.

Key features of Himalayas Remote Jobs MCP Server?

  • Access to thousands of remote job listings.
  • Real-time job and company information.
  • Advanced filtering options for job and company searches.

Use cases of Himalayas Remote Jobs MCP Server?

  1. Searching for specific remote job positions by keywords.
  2. Browsing companies that offer remote work opportunities.
  3. Comparing job opportunities across different regions.

FAQ from Himalayas Remote Jobs MCP Server?

  • Can I access jobs from any country?

Yes! You can filter jobs by country or search for worldwide remote jobs.

  • Is there a limit to the number of jobs I can search?

No, you can search for as many jobs as you need using the provided tools.

  • How do I troubleshoot connection issues?

Ensure Node.js is installed and verify your configuration matches the examples provided.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Himalayas-App
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago