LAPRAS MCP Server

Created By
lapras-inca year ago
Overview

What is LAPRAS MCP Server?

LAPRAS MCP Server is a server designed to facilitate job searches and career management by leveraging AI to process user career data and provide tailored job recommendations.

How to use LAPRAS MCP Server?

To use the LAPRAS MCP Server, you can set it up using either Node.js or Docker. You need to configure the server with your LAPRAS API key and specify the commands in a JSON configuration file.

Key features of LAPRAS MCP Server?

  • AI-driven job search capabilities
  • Integration with LAPRAS for personalized career insights
  • Support for updating and managing career information

Use cases of LAPRAS MCP Server?

  1. Searching for job opportunities based on specific criteria (e.g., remote work, salary).
  2. Updating personal career history and summaries.
  3. Generating tailored job recommendations based on user profiles.

FAQ from LAPRAS MCP Server?

  • Do I need an API key to use LAPRAS MCP Server?

Yes, an API key is required for accessing certain features related to career data.

  • Can I run LAPRAS MCP Server using Docker?

Yes, LAPRAS MCP Server can be run using Docker for better compatibility.

  • What kind of data does LAPRAS MCP Server process?

It processes personal career information and job-related queries to provide relevant results.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lapras-inc
Star
-
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)

a day ago
Crevio

2 days ago