Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
Search jobs and companies on Job Seek (jseek.co)
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"jobseek": {
"command": "npx",
"args": [
"-y",
"@jseek/mcp-server"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add jobseek -- npx -y @jseek/mcp-server프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"jobseek": {
"command": "npx",
"args": [
"-y",
"@jseek/mcp-server"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"jobseek": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@jseek/mcp-server"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 GitHub 계정 colophon-group 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.0)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Follow companies you care about. Find the right jobs. Keep your applications moving.
Job Seek brings jobs from thousands of company career pages into one search. Build watchlists, get weekly email job alerts, and track applications in one place. Free to start, with English, German, French, and Italian interfaces.
Try jseek.co → · See the features · Use the MCP server · Add a company · Run it yourself
Tracking Stripe · Anthropic · OpenAI · Figma · Vercel · Datadog · Mistral · Hugging Face · Linear · Notion · Roche · Nestlé · UBS · Swisscom · ABB · SAP · Siemens · Klarna · N26 · Wise · Monzo — and thousands more. Browse the source-of-truth registry in companies.csv.
Your next role might be at a company you already admire—or one you haven’t discovered yet. Search across employer career sites, follow a shortlist of companies, and spend less time checking the same pages for updates.
Explore without an account. Combine filters to find relevant openings across thousands of employers, from engineering and design to finance, operations, healthcare, and more.
Save a watchlist for each direction you’re considering: selected employers, a role, a location, or a combination. Enable notifications to receive a weekly email digest of new matches. Share a watchlist by link with someone else looking for similar work.
Save a job, record when you apply, add interview rounds and dates, and update the outcome. Your application tracker keeps the original job details alongside your progress; pipeline statistics help you see how the search is going.
Two roles can have the same title and very different responsibilities. Describe what matters to you in plain language:
I want to work directly with users and turn their problems into product improvements. No people management.
Narrowed checks the descriptions in your watchlist and picks out the matches. It is included with Job Seek Pro; regular search, watchlists, weekly email digests, and application tracking remain free. See Pro details and current availability.
Company pages bring together current openings, posting activity, and similar employers. Open a role at its source or use what you find to build your next watchlist.
Built by Colophon Group, a small team in Switzerland. Available in English, Deutsch, français, and italiano.
The hosted MCP endpoint exposes tools for job search, posting metadata, company lookup, filter discovery, and prefilled watchlist links. It also accepts bug reports, feature suggestions, and usability feedback through three write tools:
https://jseek.co/mcp
It uses Streamable HTTP and does not require authentication. Add the URL as a custom MCP connector, or run the published package locally:
npx @jseek/mcp-server
See packages/mcp-server/README.md for client-specific setup and tool examples. For direct HTTP integrations, the public REST contract is available at /openapi.json.
Open issues labelled company-request are companies waiting to be added. The production backlog is processed by an isolated, Hetzner-hosted Codex runner; contributors can resolve an issue with any capable coding agent that follows the repository instructions.
`ws` is an agent utility. It renders the workflow, manages isolated state, and enforces the validation gates; it is not intended as a hand-configured interactive wizard.
The environment needs git, an authenticated gh CLI, Python 3.13+, and web access. Install the workflow package:
pip install jobseek-crawler-setup
Then give your coding agent this task:
Run
ws task --issueand follow the printed instructions.
ws fetches the issue, checks for duplicates, researches the company and all relevant career boards, guides monitor and scraper selection, validates extracted data and brand assets, and opens the pull request. The registered crawler types cover common ATS APIs, sitemaps, structured data, rendered pages, PDFs, and vendor-specific formats.
No issue for the company you want? Request it. Anyone can.
The maintained workflow reference is docs/01-agent-workflow.md.
Company and board CSVs are the configuration source of truth. The crawler keeps operational state in its own Postgres database, uses Redis for scheduling, publishes searchable documents to Typesense, and stores full descriptions in S3-compatible object storage. The web app owns authentication, watchlists, and application-tracker data in a separate Postgres boundary.
%%{init: {"flowchart": {"rankSpacing": 24}}}%%
flowchart TD Requests["Company requests"] --> Agent["Coding-agent PR"] Agent --> CSV["companies.csv + boards.csv"] CSV --> Runtime["Crawler runtime sync · Redis · HTTP/browser workers · crawler Postgres"] Runtime --> ReadLayer["Published read layer Typesense · S3-compatible descriptions"] ReadLayer --> Web["Next.js web app · REST API · MCP"] Web <--> WebDB["Web Postgres"]
Start with the maintained documentation index, then read the system overview, crawler architecture, and Typesense reference.
Job Seek is self-hostable, but the repository currently expects operator-managed services. The root docker-compose.yml is development scaffolding for Postgres and Typesense, not a complete one-command production deployment.
uvThe important environment boundaries are:
| Component | Core settings |
|---|---|
| Crawler database | LOCAL_DATABASE_URL |
| Web database | WEB_DATABASE_URL for crawler-side reads; DATABASE_URL for the web app |
| Redis | REDIS_URL |
| Typesense writes | TYPESENSE_HOST, TYPESENSE_PORT, TYPESENSE_PROTOCOL, TYPESENSE_OPERATIONS_KEY |
| Typesense web access | TYPESENSE_SEARCH_KEY, TYPESENSE_WRITE_KEY, and optionally TYPESENSE_BROWSER_PARENT_KEY |
| Description storage | R2_ENDPOINT_URL, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_BUCKET, R2_DOMAIN_URL |
| Web authentication | BETTER_AUTH_SECRET, BETTER_AUTH_URL; OAuth and email providers are optional |
After provisioning those services, create apps/crawler/.env.local (using its .env.example as a starting point) and apps/web/.env.local, then initialize in this order:
git clone https://github.com/colophon-group/jobseek
cd jobseek corepack enable pnpm install
cd apps/web pnpm db:migrate
cd ../crawler uv sync uv run playwright install chromium-headless-shell # required by run-browser uv run alembic -c src/migrations/alembic.ini upgrade head uv run crawler setup-typesense uv run crawler sync
A complete crawler deployment keeps four process roles running:
uv run crawler run # HTTP workers
uv run crawler run-browser # Playwright workers uv run crawler export # Postgres → Typesense CDC uv run crawler drain # descriptions → object storage
Start the frontend separately from apps/web:
pnpm dev # http://localhost:3000
Production operators should use scoped Typesense keys and read the deployment and recovery runbooks linked from docs/README.md.
apps/crawler/ Python ingestion, normalization, scheduling, and export
src/core/monitors/ Career-board discovery: ATS APIs, sitemaps, DOM, feeds src/core/scrapers/ Posting extraction: JSON-LD, DOM, PDF, vendor formats src/workers/ HTTP workers, browser workers, and description drain src/exporter.py CDC from crawler Postgres to Typesense src/labeller/ Daily gold-dataset labelling and Hugging Face upload src/workspace/ ws workflow and Codex company-request runner data/companies.csv Company configuration source of truth data/boards.csv Career boards with monitor + scraper configuration
apps/web/ Next.js 16, Drizzle, Lingui, and Better Auth app/[lang]/ Localized product routes: en / de / fr / it app/api/v1/ Public REST API app/mcp/ Hosted Streamable HTTP MCP endpoint src/db/schem
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요