--- title: "MCP 서버: Claude, ChatGPT, Cursor를 실시간 채용 공고에 연결 | Metaintro" canonical: "https://beta.metaintro.com/ko/developers/mcp" language: "ko" author: "Metaintro" --- MCP 서버 · 무료 # AI를 Metaintro에 연결하세요 Claude, ChatGPT, Cursor 등 모든 MCP 클라이언트에 실시간 채용 공고, 기업 정보, 시장 데이터를 제공합니다. 로그인하면 프로필, 이력서, 관리 중인 채용 공고, 다음 단계까지 내 구직 활동도 맡길 수 있습니다. [클라이언트에 추가하기](#setup)[도구 둘러보기](#tools) 모든 연결이 무료입니다. 검색에는 계정이 필요 없습니다. _Claude Code에서 사용해 보기_ ``` claude mcp add --transport http metaintro-public https://www.metaintro.com/api/mcp/public ``` 연결 ## 주소 세 개, 주소마다 다른 접근 범위 주소에 따라 에이전트가 접근할 수 있는 범위가 정해집니다. 공개 주소로 시작하고, 내 구직 활동을 맡기고 싶을 때 로그인하세요. - 로그인 불필요 ### 공개 서버 주소`https://www.metaintro.com/api/mcp/public` 실시간 채용 공고, 비슷한 채용 공고, 기업 프로필, 기업별 채용 중인 직무, 내 주변에서 채용 중인 기업, 검색별 채용 시장 정보. 읽기 전용입니다. **로그인**: 필요 없음. 도구 호출은 네트워크 주소당 분당 최대 30회입니다. **도구 수**: 7 - 내 계정 ### 개인 서버 주소`https://www.metaintro.com/api/mcp` 내 구직 활동: 프로필, 이력서, 관리 중인 채용 공고, 다음 단계, 지원 기록, 알림, 문서, Metaintro 어시스턴트와의 채팅. search_actions와 run_action으로 허용된 다른 모든 작업도 할 수 있습니다. **로그인**: OAuth로 로그인하거나 설정 > 에이전트에서 만든 개인 API 키를 사용하세요. **도구 수**: 59 - 직원 ### 조직 서버 주소`https://www.metaintro.com/api/mcp/org/` 케이스 매니저와 직원용이며, 소속 조직의 회원만 다룹니다. 담당 사례, 작업 대기열, 알림, 메모, 정기 점검, 약속 사항, 회원 채용 보드, 이메일로 보내는 채용 목록, 취업 실적 및 성과 보고서, 작업, 실시간 채용 검색, Cabinet의 채용 검색 및 초안 작성 도구. **로그인**: 직원으로 로그인. 조직의 정확한 주소는 해당 조직의 설정 > 에이전트에 있습니다. **도구 수**: 92 설정 ## 클라이언트에 추가하기 대부분의 클라이언트는 알아서 로그인을 안내합니다. 주소를 추가한 뒤 브라우저에서 로그인을 승인하면 됩니다. 계정 없이 검색하려면 공개 주소를 사용하세요. ``` ## ClaudeClaude 앱이나 claude.ai에서 설정 > 커넥터를 열고 맞춤 커넥터 추가를 선택하세요. 이름을 Metaintro로 지정하고 주소를 붙여넣으세요.## ChatGPTChatGPT에서 설정 > 커넥터를 열고 주소로 맞춤 커넥터를 만드세요. 로그인 방식을 물으면 OAuth를 선택하세요.> 요금제에 따라 맞춤 커넥터를 쓰려면 개발자 모드나 작업 공간 관리자의 승인이 필요할 수 있습니다.내 구직 활동, 로그인 필요: `https://www.metaintro.com/api/mcp`검색 전용, 로그인 불필요: `https://www.metaintro.com/api/mcp/public` ``` Cursor에 설치VS Code에 설치 개인 연결을 설치합니다. 클라이언트가 로그인을 요청합니다. ### API 키를 쓰고 싶으신가요? 설정 > 에이전트에서 개인 키를 만들고 Authorization: Bearer 헤더로 보내세요. 키를 가진 사람은 누구나 사용자로서 작업할 수 있으니 공유 파일이나 채팅에 넣지 마세요. [키 만들기](/ko/settings/agents) 도구 레퍼런스 ## 에이전트가 보는 그대로의 모든 도구 이름과 설명은 서버가 에이전트에 보내는 내용 그대로이므로 영어로 표시됩니다. MCP Apps를 지원하는 클라이언트는 채용 결과를 대화형 채용 카드로 보여 줍니다. **공개 도구7** - `search_jobs`읽기채용 카드 Search jobs Search live job postings from employer career sites and job boards by what the person is looking for, with optional filters for title, location, remote work and pay. Returns up to 10 job cards a page; page with offset or cursor. Each job opens at https://www.metaintro.com/job/; read one in full with get_job, and its employer with get_company and the job's companySlug. - `get_job`읽기채용 카드 Read a job posting Read one job posting in full, by the id a search returned: description, requirements, pay, location and the employer's apply link. - `get_market_insights`읽기 Read the job market for a search Summarize the live job market for a search: how many jobs match, the median listed pay, the most common work arrangement and the top requested skills, with how the search was understood. Takes the same query and filters as search_jobs. - `get_company`읽기 Read a company Read an employer's profile by its slug (companySlug on a job): what it does, size, how it is hiring (open roles, 30-day change, departments, locations, remote share, how long roles stay open), observed pay bands, work arrangement, benefits and recent events. Its page is https://www.metaintro.com/company/. - `list_company_jobs`읽기채용 카드 List a company's open jobs List an employer's open jobs by its slug, newest first. Page with cursor. - `find_similar_jobs`읽기채용 카드 Find similar jobs Find live jobs like one job, by the id a search returned: the same kind of role in the same place (or remote, when the job is remote), as up to 10 job cards. Use it when a job is closed, a near miss, or the person wants more like it. - `get_local_demand`읽기 Read local job demand Read which kinds of roles are hiring most in a place (city, region, country): open jobs by role category, with total open jobs, employers and sectors. When a place has too few role types it widens to the region, the country or worldwide; scope and locationLabel say which. Use it when someone does not yet know what to look for. **개인 도구59** - `chat`쓰기 Chat with Metaintro Send a text message to Metaintro’s personal assistant. Omit threadId to start a conversation; pass the returned threadId to continue. Uses the same assistant and tools as the app for job discovery, résumé building and tailoring, interview preparation, and profile help. Returns the reply and artifacts. Requires write access because the assistant can update your data. Use the messaging actions for shared conversations; your approval preference applies. If interrupted, read_thread before retrying; never resend blindly. - `whoami`읽기 Who am I Who this agent acts as, what its key may do, and the organizations where the person works as staff (with each one's slug and id, which the case manager tools take). Call it first. - `search_actions`읽기 Search actions Find any action this agent can run beyond the named tools: everything a job seeker or a case manager can do in Metaintro. Returns each action's name, whether it reads, writes or needs a person's approval, and its inputSchema. Run one with run_action. - `get_action_request`읽기 Check a waiting action Read one action your agent asked for that waits for you: whether it is still waiting, approved and done, declined or expired, and its result once it ran. Takes the request id a held call returned. - `run_action`쓰기 Run an action Run one action that search_actions found, with its input. It runs as you, with the same access you have in the app. Your approvalMode from whoami determines whether a write runs immediately or waits for approval. Reads run immediately. - `get_my_profile`읽기 Read my profile Read your master profile: experience, skills, education, preferences, and its version number (pass it as expectedVersion when you change it). - `update_profile_section`쓰기 Replace a profile section Replace one section of your master profile. Read the profile first and pass its version as expectedVersion; a stale version is refused so nothing newer is overwritten. - `update_profile_fields`쓰기 Change profile fields Change individual fields of your master profile with set, append, remove or upsert operations. Pass the profile's current version as expectedVersion. - `list_profile_changes`읽기 List profile changes List earlier versions of your master profile, newest first, with who or what changed it. - `get_search_preferences`읽기 Read my search preferences Read the saved search filters and last search your job matching runs on. Pay and dealbreakers are in your profile. - `update_dealbreakers`쓰기 Set dealbreakers Set the things a job must not have. Pass the profile's current version as expectedVersion. - `update_compensation`쓰기 Set pay expectations Set the pay you are looking for. Pass the profile's current version as expectedVersion. - `get_master_resume`읽기 Read my master résumé Read your primary résumé, the one Metaintro tailors from, with its content and design. - `list_resumes`읽기 List my résumés List the résumés you built in Metaintro. - `get_resume`읽기 Read a résumé Read one résumé you built, by its id. - `update_resume`쓰기 Edit a résumé Change a résumé's content. Pass the updatedAt you read as expectedUpdatedAt so an edit made elsewhere is not overwritten. Set createVersion to keep the old text as a version. - `list_uploaded_resumes`읽기 List uploaded résumé files List the résumé files you uploaded. - `create_resume`쓰기 Build a résumé from my profile Build a résumé from your existing master profile. To create or tailor one conversationally, use chat. - `export_resume`쓰기 Export a résumé as PDF Export one of your résumés as a PDF for you to download. This does not submit an application. - `set_master_resume`쓰기 Choose my master résumé Choose which of your résumés is the primary résumé used for tailoring. - `duplicate_resume`쓰기 Copy a résumé Make an editable copy of one of your résumés. - `list_resume_versions`읽기 List résumé versions Read the saved versions of one of your résumés before restoring or editing it. - `get_resume_download`읽기 Download an uploaded résumé Get a download URL for one of your uploaded résumé files. Treat the returned URL as private. - `search_jobs`읽기채용 카드 Search jobs Search live job postings from employer career sites and job boards by what the person is looking for, with optional filters for title, location, remote work and pay. Returns up to 10 job cards a page; page with offset or cursor. Each job opens at https://www.metaintro.com/job/; read one in full with get_job, and its employer with get_company and the job's companySlug. - `get_job`읽기채용 카드 Read a job posting Read one job posting in full, by the id a search returned: description, requirements, pay, location and the employer's apply link. - `get_market_insights`읽기 Read the job market for a search Summarize the live job market for a search: how many jobs match, the median listed pay, the most common work arrangement and the top requested skills, with how the search was understood. Takes the same query and filters as search_jobs. - `get_company`읽기 Read a company Read an employer's profile by its slug (companySlug on a job): what it does, size, how it is hiring (open roles, 30-day change, departments, locations, remote share, how long roles stay open), observed pay bands, work arrangement, benefits and recent events. Its page is https://www.metaintro.com/company/. - `list_company_jobs`읽기채용 카드 List a company's open jobs List an employer's open jobs by its slug, newest first. Page with cursor. - `find_similar_jobs`읽기채용 카드 Find similar jobs Find live jobs like one job, by the id a search returned: the same kind of role in the same place (or remote, when the job is remote), as up to 10 job cards. Use it when a job is closed, a near miss, or the person wants more like it. - `get_local_demand`읽기 Read local job demand Read which kinds of roles are hiring most in a place (city, region, country): open jobs by role category, with total open jobs, employers and sectors. When a place has too few role types it widens to the region, the country or worldwide; scope and locationLabel say which. Use it when someone does not yet know what to look for. - `list_matched_jobs`읽기 List jobs matched to me List the jobs Metaintro matched to you. Set newOnly to see only ones you have not opened. Page with cursor. - `get_next_steps`읽기 What to do next Read what needs doing in your job search, most urgent first: interviews in the next two days (INTERVIEW), reminders that are due (REMINDER), application deadlines within a week (DEADLINE), postings that closed while you were applying (CLOSED_POSTING), applications with no news for 14 days (NO_ACTIVITY) and applications started but not confirmed (UNCONFIRMED_APPLICATION). Each item names its tracked job. Also returns how many jobs sit in each stage, your weekly momentum and, in a program, this week's goals. Call it at the start of a session. - `list_my_jobs`읽기 List my jobs List every job and lead you are tracking, grouped by stage. - `get_my_job`읽기 Read one of my jobs Read one tracked job or lead in full, with its notes, contacts, interviews, offer and reminders. - `check_resume_fit`쓰기 Check my résumé against a job Score how well your base résumé fits a tracked job and save the score and its details on the job. savedJobId comes from list_my_jobs. Refused until you have uploaded a résumé. - `save_job`쓰기 Save a job or lead Start tracking a job or a lead. Saving the same job again updates supplied fields, including title and company, and records another save activity. idempotencyKey does not deduplicate saves; read the tracked job before retrying a call whose outcome is unknown. - `update_my_job`쓰기 Update a tracked job Move a tracked job to another stage, or change its pay, location, note or interview. - `add_job_note`쓰기 Add a note to a job Add a note to a tracked job or lead. - `record_application`쓰기 Record an application Record that you applied to a tracked job: how, when, and with which résumé. - `set_job_reminder`쓰기 Set a job reminder Set a reminder on a tracked job, such as a follow-up date. - `get_weekly_work_search`읽기 Read my weekly work search Read one week of your work search activity, as unemployment programs ask for it. Only for people an organization enrolled in its work-search program (whoami's workSearchProgram.enrolled); anyone else is refused, so don't offer it to them. - `export_weekly_work_search`쓰기 Export my weekly work search Export one week of your work search as CSV (week is current or that week's start date, YYYY-MM-DD), to attach to an unemployment claim's weekly certification. Same program rule as get_weekly_work_search. - `set_email_preferences`쓰기 Change my emails and notifications Turn Metaintro's emails and push notifications on or off. similarJobsEnabled emails new jobs like the ones you saved (Metaintro's job alerts); careerDigestEnabled the career digest; caseThreadEmailEnabled email from your case manager's conversation; pushNotificationsEnabled phone notifications; marketingEnabled, partnerIntrosEnabled and onboardingEmailsEnabled the rest. Send only the switches to change; it returns them all. - `get_memory`읽기 Read what Metaintro remembers Read the things Metaintro's chat has remembered about you and your search. - `list_threads`읽기 List my conversations List your conversations, newest first. Page with cursor. - `read_thread`읽기 Read a conversation Read the messages in one of your conversations, including your case manager's. Page with cursor. - `record_job_contact`쓰기 Save a job contact Save a contact on a tracked job. This records information; it does not contact the person. - `record_interview`쓰기 Record an interview Record an interview and its details on a tracked job. Use chat for interview preparation. - `record_offer`쓰기 Record a job offer Record offer terms on a tracked job. This does not accept or decline an offer with the employer. - `record_follow_up`쓰기 Record a follow-up Record a follow-up you already made on a tracked job. This does not send a message. - `update_job_reminder`쓰기 Update a job reminder Update or complete an existing reminder for a tracked job. - `list_application_materials`읽기 List application materials Read the résumé and supporting documents prepared for a tracked job. - `get_job_document`읽기 Read an application document Read a saved application document such as a cover letter or interview notes. - `save_job_document`쓰기 Save an application document Save document content on one of your tracked jobs, using the version fields in the schema to avoid overwriting newer work. - `export_job_document`쓰기 Export an application document Export a prepared document for your own use. This does not send it to an employer. - `check_job_availability`쓰기 Check whether a job is open Check the availability of a job you are tracking before applying. - `get_case_manager`읽기 Read my case manager's status See who your case manager is on a conversation and whether a request to them is open. - `message_case_manager`쓰기 Message my case manager Request a message to your case manager in one of your conversations. Your approval setting decides whether it waits for you; pass reason so you can tell what you are approving. Pass a stable clientMessageId so a retry sends it once. - `request_case_manager`쓰기 Ask for my case manager Ask your case manager to join a conversation, with an optional message and priority. search_actions와 run_action으로 쓸 수 있는 추가 작업183 **조직 도구92** - `whoami`읽기 Who am I Who this agent acts as, what its key may do, and the organizations where the person works as staff (with each one's slug and id, which the case manager tools take). Call it first. - `search_actions`읽기 Search actions Find any action this agent can run beyond the named tools: everything a job seeker or a case manager can do in Metaintro. Returns each action's name, whether it reads, writes or needs a person's approval, and its inputSchema. Run one with run_action. - `get_action_request`읽기 Check a waiting action Read one action your agent asked for that waits for you: whether it is still waiting, approved and done, declined or expired, and its result once it ran. Takes the request id a held call returned. - `run_action`쓰기 Run an action Run one action that search_actions found, with its input. It runs as you, with the same access you have in the app. Your approvalMode from whoami determines whether a write runs immediately or waits for approval. Reads run immediately. - `search_jobs`읽기채용 카드 Search jobs Search live job postings from employer career sites and job boards by what the person is looking for, with optional filters for title, location, remote work and pay. Returns up to 10 job cards a page; page with offset or cursor. Each job opens at https://www.metaintro.com/job/; read one in full with get_job, and its employer with get_company and the job's companySlug. - `get_job`읽기채용 카드 Read a job posting Read one job posting in full, by the id a search returned: description, requirements, pay, location and the employer's apply link. - `get_market_insights`읽기 Read the job market for a search Summarize the live job market for a search: how many jobs match, the median listed pay, the most common work arrangement and the top requested skills, with how the search was understood. Takes the same query and filters as search_jobs. - `get_company`읽기 Read a company Read an employer's profile by its slug (companySlug on a job): what it does, size, how it is hiring (open roles, 30-day change, departments, locations, remote share, how long roles stay open), observed pay bands, work arrangement, benefits and recent events. Its page is https://www.metaintro.com/company/. - `list_company_jobs`읽기채용 카드 List a company's open jobs List an employer's open jobs by its slug, newest first. Page with cursor. - `find_similar_jobs`읽기채용 카드 Find similar jobs Find live jobs like one job, by the id a search returned: the same kind of role in the same place (or remote, when the job is remote), as up to 10 job cards. Use it when a job is closed, a near miss, or the person wants more like it. - `get_local_demand`읽기 Read local job demand Read which kinds of roles are hiring most in a place (city, region, country): open jobs by role category, with total open jobs, employers and sectors. When a place has too few role types it widens to the region, the country or worldwide; scope and locationLabel say which. Use it when someone does not yet know what to look for. - `list_members`읽기 List members List an organization's members you may see, with stage, status, case manager, last contact and next action. Filter and sort; page with cursor. - `find_member`읽기 Find a member Find members of an organization by name or email. - `get_member`읽기 Read a member Read one member's record in an organization. - `get_member_profile`읽기 Read a member's profile Read a member's master profile. - `get_member_brief`읽기 Read a member's brief Read the latest brief on a member: where their search stands and what to do next. Use it as a handoff summary. - `generate_member_brief`쓰기 Write a fresh member brief Write a fresh brief on a member from their current record, for a handoff or a meeting. - `get_what_matters`읽기 Read what matters to a member Read the lines on what matters most in a member's search. Until staff save their own list, they come from the latest brief. - `set_what_matters`쓰기 Set what matters to a member Replace the lines on what matters most in a member's search. Send every line to keep, with source STAFF for any line you wrote or changed. - `list_member_activity`읽기 List a member's activity List a member's timeline: notes, check-ins, outreach, applications and stage changes. Page with cursor. - `add_member_note`쓰기 Add a note on a member Add a note to a member's record. Every note is stored the same way; type is recorded only in the audit log. - `log_check_in`쓰기 Log a check-in Log a check-in you had with a member: the day, how, which direction, a note and the next follow-up date. - `list_check_ins`읽기 List check-ins List an organization's check-ins, by status and owner. - `log_outreach`쓰기 Log outreach Record contact with an employer or anyone else on a member's behalf: the channel, the direction, what was said and when. - `update_pipeline_stage`쓰기 Move a member's stage Move a member to another pipeline stage: intake, searching, résumé building, applying, interviewing, offer or placed. - `update_member_status`쓰기 Change a member's status Change a member's status in the organization. Depending on the person's approval setting it may wait for approval; pass reason so they can tell what they are approving. - `assign_case_manager`쓰기 Assign a case manager Assign a member to a case manager. Depending on the person's approval setting it may wait for approval; pass reason so they can tell what they are approving. - `list_case_managers`읽기 List case managers List an organization's active case managers by name, up to 100 a page, with each one's caseload. Narrow it with search (part of a name or email) or staffIds; pass nextCursor back as cursor for the next page. - `list_job_lists`읽기 List job lists sent List the job lists sent to a member, newest first, with how many roles reached each status. Pass nextCursor back as cursor for older lists; read one list's roles with get_job_list. - `get_job_list`읽기 Read a job list Read one job list in full: each role, its status and feedback, and the attachments sent with it. - `update_role_status`쓰기 Update a role's status Record where a member stands on a role from a job list you sent them. - `get_member_job_board`읽기 Read a member's jobs Read every job and lead a member is tracking, by stage. - `move_member_job`쓰기 Move a member's job Move a job on a member's My jobs board to another stage: SAVED, APPLYING, APPLIED, INTERVIEWING or OFFERED, or close it as ACCEPTED, REJECTED, WITHDRAWN or NO_REPLY. Activity records you as the one who moved it. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `add_member_job_note`쓰기 Add a note to a member's job Add a note to a job on a member's board. The member and your team see it, signed with your name. savedJobId is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `record_member_application`쓰기 Record a member's application Record that a member applied to a job on their board: how, when (appliedAt) and with which résumé. Moves a saved job to APPLIED. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `set_member_job_reminder`쓰기 Set a reminder on a member's job Set a reminder on a job on a member's board, such as a follow-up date. The member sees it. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `update_member_job_reminder`쓰기 Update a reminder on a member's job Complete, cancel or snooze a reminder on a member's job. Snooze needs snoozedUntil. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `record_member_job_contact`쓰기 Record a contact on a member's job Add or update a person on a member's job: a recruiter, hiring manager or referrer. Pass contactId to update one. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `record_member_interview`쓰기 Record an interview on a member's job Add or update an interview round on a member's job: when, format and outcome. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `record_member_offer`쓰기 Record an offer on a member's job Record or update an offer on a member's job: pay, start date, decision deadline and outcome. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `archive_member_job`쓰기 Archive a member's job Take a job off a member's board. restore_member_job puts it back. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `restore_member_job`쓰기 Restore a member's job Put an archived job back on a member's board. id is the job's id from get_member_job_board. Pass provenance when the change comes from something the member said or sent: a note on why, the channel, when they told you (reportedAt) and when it actually happened (occurredAt, which dates the event). The member can see this record. - `log_off_list_application`쓰기 Log an application Record an application a member made to a job that was not on a list you sent. - `get_work_queue`읽기 Read my work queue Read the organization's work queue: what is waiting on staff, block by block. Each block holds its first rowsPerBlock rows (25 unless you ask for up to 50), its total (null when only a lower bound is known) and whether more are waiting. - `list_reply_queue`읽기 List members waiting on a reply List members whose newest message waits on a staff reply. - `read_member_thread`읽기 Read a member's conversation Read one of a member's conversations. Page with cursor. - `add_staff_note`쓰기 Add a staff-only note Add a note on a member's conversation that only staff see. The member never sees it. - `list_tasks`읽기 List tasks List an organization's tasks, by status and owner. - `create_task`쓰기 Create a task Create a task, optionally for a member, with a due date. - `update_task_status`쓰기 Change a task's status Change a task's status. - `list_placements`읽기 List placements List an organization's placements (a member's path to a specific job: SOURCING, INTERVIEWING, OFFER, PLACED), newest first, with the member and counts by stage. Filter by stage or memberId; page with page and pageSize (up to 100). - `list_placement_options`읽기 List placements to link List recent placements as short labels (role • company, and the member's name) with their ids, to link a task to one as placementId. - `record_placement`쓰기 Record a placement Record a member's path to a specific job: roleTitle and companyName, the stage (SOURCING unless you say otherwise; PLACED when they were hired), notes and where the role came from (source). Placements are what an organization's outcomes are counted from, so record a hire as PLACED. - `move_placement_stage`쓰기 Move a placement's stage Move a placement to SOURCING, INTERVIEWING, OFFER or PLACED. Pass occurredAt when it happened earlier than now, such as the member's start date. Moving to PLACED counts the member as placed and resolves the placement's stalled alert. - `update_placement`쓰기 Update a placement Correct a placement's role, company, stage, notes or source. Send every field you want to keep; read it with list_placements first. - `get_outcomes_overview`읽기 Read outcomes at a glance Read an organization's outcomes for a period: caseload, new members, members placed, check-ins completed, staff contacts, median reply time, members gone quiet and how many sit at each stage. window sets the period: from and to as YYYY-MM-DD (at most 366 days apart), timeZone as an IANA name such as America/Chicago, unit (day, week or month) for the trend, and weekStart (0 for Sunday, 1 for Monday). Each figure comes with the previous period of the same length, so say what changed. A case manager without broad access sees their own caseload (scope caseload); sample true means the numbers are demonstration data. - `get_placements_report`읽기 Read the placements report Read placements for a period: members placed, placements and offers, median days to placed, open placements by stage, top employers and the most recent placements. window sets the period: from and to as YYYY-MM-DD (at most 366 days apart), timeZone as an IANA name such as America/Chicago, unit (day, week or month) for the trend, and weekStart (0 for Sunday, 1 for Monday). Each figure comes with the previous period of the same length, so say what changed. A case manager without broad access sees their own caseload (scope caseload); sample true means the numbers are demonstration data. - `get_pipeline_report`읽기 Read the pipeline report Read how members move through the pipeline in a period: members at each stage, moves forward and backward, and median days to placed. window sets the period: from and to as YYYY-MM-DD (at most 366 days apart), timeZone as an IANA name such as America/Chicago, unit (day, week or month) for the trend, and weekStart (0 for Sunday, 1 for Monday). Each figure comes with the previous period of the same length, so say what changed. A case manager without broad access sees their own caseload (scope caseload); sample true means the numbers are demonstration data. - `get_engagement_report`읽기 Read the engagement report Read how engaged members were in a period: how many were active, what they did (searched, wrote a message, saved a job, applied, had an interview, got an offer) and the searches they ran most. window sets the period: from and to as YYYY-MM-DD (at most 366 days apart), timeZone as an IANA name such as America/Chicago, unit (day, week or month) for the trend, and weekStart (0 for Sunday, 1 for Monday). Each figure comes with the previous period of the same length, so say what changed. A case manager without broad access sees their own caseload (scope caseload); sample true means the numbers are demonstration data. - `get_case_work_report`읽기 Read the case work report Read the staff's case work in a period: check-ins, contacts by channel, job lists sent, outreach, reply times and each staff member's share. window sets the period: from and to as YYYY-MM-DD (at most 366 days apart), timeZone as an IANA name such as America/Chicago, unit (day, week or month) for the trend, and weekStart (0 for Sunday, 1 for Monday). Each figure comes with the previous period of the same length, so say what changed. A case manager without broad access sees their own caseload (scope caseload); sample true means the numbers are demonstration data. - `list_promises`읽기 List what you promised a member List the promises staff made to a member, open and kept, each with its owner and due date, and whose turn it is in the conversation. Read it before a meeting so nothing promised is forgotten. - `add_promise`쓰기 Record a promise to a member Record something you promised a member, such as sending three warehouse roles by Friday, with a due date (YYYY-MM-DD, or null) and a stable submissionId so a retry records it once. It becomes the member's next action until it is kept. - `set_promise_kept`쓰기 Mark a promise kept Mark a promise to a member kept, or open again with kept false. promiseId comes from list_promises. - `list_alerts`읽기 List alerts List an organization's alerts, newest first: unanswered replies (THREAD_REPLY), overdue or due next actions, members gone quiet, sent job lists with no answer, stalled stages, new members and job card outcomes or feedback. Filter by status (OPEN, ACKNOWLEDGED, RESOLVED) or eventType; page with cursor. Alert types you muted are left out. - `acknowledge_alert`쓰기 Acknowledge an alert Acknowledge an alert: you have seen it and it stays open until it is resolved. - `resolve_alert`쓰기 Resolve an alert Resolve an alert once what it asked for is done. Needs permission to manage the organization. - `snooze_alert`쓰기 Snooze an alert Hide an alert until a date and time (until, ISO 8601), such as the day after a scheduled check-in. - `list_recommendations`읽기 List recommendations for a member List the recommendations on a member's record: prompts to try next, jobs to save, check-ins, follow-up tasks and profile corrections. Filter by status (OPEN, RESOLVED) or threadId. Staff see them on the member's record. - `recommend_for_member`쓰기 Add a recommendation for a member Add a recommendation to a member's record for the team to act on: type NEXT_PROMPT, SAVED_JOB, CHECK_IN, FOLLOW_UP_TASK or PROFILE_CORRECTION, a short title, a description, an optional link (url) and due date (dueAt). - `resolve_recommendation`쓰기 Resolve a recommendation Resolve a recommendation once it is done. recommendationId comes from list_recommendations. - `update_check_in_status`쓰기 Change a check-in's status Mark a scheduled check-in COMPLETED, NO_SHOW or RESCHEDULE, or back to SCHEDULED. id comes from list_check_ins. To record what was said, use log_check_in. - `update_task`쓰기 Update a task Change a task's title, description, member, priority, due date or status. Send every field you want to keep; read it with list_tasks first. - `list_member_threads`읽기 List a member's conversations List a member's recent conversations you may see, newest first, and which one is their case conversation (the one staff and the member share). Read one with read_member_thread. - `open_case_thread`쓰기 Open a member's case conversation Return the member's case conversation, starting it if they have none yet. Returns its threadId and whether it was created. Job list rounds and staff messages go here. - `get_member_work_search`읽기 Read a member's work-search weeks Read a member's weekly work-search record for an unemployment program, newest week first (12 unless you pass limit, up to 52): activities, applications and whether each week met the requirement. Only where the organization keeps work-search evidence. - `export_member_work_search`쓰기 Export a member's work-search record Export a member's work-search activities as CSV, for a program's weekly certification. Needs permission to export data. Depending on the person's approval setting it may wait for approval; pass reason naming the member. - `log_job_list`쓰기 Log a job list sent outside Metaintro Record a job list you already gave a member some other way (email, WhatsApp, in person): the roles (title, employer, location, pay, apply link), when it was sent and a note. Nothing is sent. To send roles to a member from Metaintro, use start_job_list_round. - `add_job_list_roles`쓰기 Add roles to a logged job list Add roles to a job list you logged with log_job_list. Nothing is sent. - `start_job_list_round`쓰기 Start a job list for a member Start the next job list round to email a member; it returns the round's jobListId. Each call starts a new round and carries over roles not yet sent, so first call preview_job_list_round without jobListId: when it returns a round, add to that one. Then add roles with add_job_list_round_role, read it with preview_job_list_round and send it with send_job_list_round. threadId is the member's case conversation, from open_case_thread. - `add_job_list_round_role`쓰기 Add a role to a job list round Add a role to an unsent job list round: title, employer, location, pay (comp), the apply link (applyUrl, required, checked before it is added; a closed posting is refused), why it fits the member (whyFits) and any catch (catchNote). A role already in the round (same employer, title, location, pay and posted date) is kept as it is and returns duplicate: true; only a new apply link replaces the old one, so get whyFits and catchNote right the first time. Use roles from search_jobs or find_similar_jobs and name the evidence in whyFits. threadId is the member's case conversation, from open_case_thread. - `preview_job_list_round`읽기 Preview a job list round Read the email a job list round will send: subject, the roles that will go and the ones skipped or held, the member's constraints it was checked against, and contentHash. Show it to the case manager before sending. round is null when nothing is waiting to send. threadId is the member's case conversation, from open_case_thread. - `send_job_list_round`쓰기 Send a job list round Email a job list round to the member, signed with your name. Pass the contentHash from preview_job_list_round; if the list changed since, it is refused and you preview again. Depending on the person's approval setting it may wait for approval; pass reason naming the member and the roles. threadId is the member's case conversation, from open_case_thread. - `show_results`읽기 show results Cabinet: Show what has already been found and learned for one job seeker: what we know about them and what is still missing, the questions to ask them, what their recent job searches found and why, and the newest reply drafted for them. Use it first for any question about one person, such as why they have no new jobs, what to ask them, what was found for them, or what was drafted. It reads what exists and starts no new work. - `get_status_report`쓰기 get status report Cabinet: Write a new status report on the job seekers: what changed, who is waiting, and who to focus on first. The report the case manager is reading is already in the conversation. Call this only when the case manager asks for a report: a fresh one, one since a date, or one about one person. For a question about one person, use show_results instead. It takes up to half a minute. - `find_jobs`쓰기 find jobs Cabinet: Look for jobs for some of the job seekers, or for everyone. Use it when the case manager asks to find, search for, or look for work for somebody. Each search runs on its own and takes a few minutes. - `draft_replies`쓰기 draft replies Cabinet: Draft the next message to some of the job seekers, or to everyone. Use it when the case manager asks to draft, write, reply to, or check in with somebody. Nothing is sent: each draft waits until the case manager asks to send it. - `send_replies`쓰기 send replies Cabinet: Send the drafted replies to some of the job seekers, or to everyone with a draft waiting. Use it only when the case manager asks to send, such as send it, send Marisol's draft, or send the replies. Each person gets the newest draft written for them in the last two weeks, as it was written, with its roles. A draft goes nowhere when somebody already replied after it, or when the person wrote after it. - `check_progress`읽기 check progress Cabinet: How a search or a draft placed in this chat is going: who is finished, and what came of it. Use it when the case manager asks how it is going, or whether it is done. - `cancel_request`쓰기 cancel request Cabinet: Stop a search or a draft placed in this chat. Work already running stops at its next step, and what it wrote stays. - `list_job_seekers`읽기 list job seekers Cabinet: Who is on the caseload and where each one stands: their stage, how long since anybody reached them, what is booked next, what they want, and what blocks them. Narrow it to the people a question is about. - `read_activity`읽기 read activity Cabinet: Who on the caseload did something over the last days, or did not, person by person. It reads the whole caseload at once, however many people are on it. Use it for questions such as who searched for jobs this week, who has not applied in a month, who has been most active, who did nothing at all, or what Andy and Lena did lately. It answers with how many matched, and lists up to 100 of them with everything each did, when, and the jobs they searched for. Leave activity out to look at everything. - `count_activity`읽기 count activity Cabinet: How many people on the caseload did each thing over the last days, and how many times, with the job titles they searched for most. It reads the whole caseload at once. Use it for questions such as how many people applied this month, what people are searching for, how activity changed week by week, or which stage or city is most active. search_actions와 run_action으로 쓸 수 있는 추가 작업271 프롬프트 ## 바로 쓰는 워크플로 MCP 프롬프트를 지원하는 클라이언트는 이를 명령으로 보여 줍니다. 하나를 고르면 에이전트가 위의 도구로 워크플로를 시작합니다. ### 공개 - `find_jobs_that_fit`Find jobs that fit A short list of live jobs that fit what you want, with what still needs checking. 인수: role, location (선택 사항) - `explore_careers`Explore jobs near me What is hiring where you live, and which of those roles suit you. 인수: location ### 개인 - `plan_my_day`Plan my job search today What needs doing today: interviews, due reminders, deadlines, stale applications and new matches. - `find_jobs_that_fit`Find jobs that fit A short list of live jobs that fit what you want, with what still needs checking. 인수: role, location (선택 사항) - `explore_careers`Explore jobs near me What is hiring where you live, and which of those roles suit you. 인수: location - `tailor_resume_for_job`Tailor my résumé to a job A copy of your master résumé tailored to one job, ready to export. 인수: jobId - `prepare_for_interview`Prepare for an interview A briefing on the company and role, likely questions and stories from your experience. 인수: savedJobId - `weekly_review`Review my week What you did this week, what came of it and what to change next week. ### 조직 - `triage_my_caseload`Triage my caseload Who needs you first today and the one action that moves each of them. - `prepare_member_meeting`Prepare for a member meeting A one-page briefing on a member: where their search stands and what to agree next. 인수: memberId - `find_jobs_for_member`Find jobs for a member Live roles that fit a member, checked against what matters to them, ready to send as a job list. 인수: memberId - `report_outcomes`Report our outcomes A short outcomes report for a period: placements, engagement and case work, with what changed. 인수: period (선택 사항) 안전한 설계 ## 에이전트는 오직 사용자 본인으로서만 작동합니다 모든 연결과 모든 클라이언트에 같은 규칙이 적용됩니다. - ### 한 사람으로서 작동 연결은 로그인한 사람으로서, 그 사람의 권한 안에서만 작동합니다. - ### OAuth와 권한 범위 동적 클라이언트 등록과 PKCE를 사용하는 OAuth 2.1 또는 개인 키로 로그인합니다. 읽기와 쓰기는 mcp.read와 mcp.write라는 별도의 권한 범위입니다. - ### 보류할 작업은 사용자가 결정 승인 설정에 따라 에이전트 작업을 바로 실행하거나, 민감한 작업만 보류하거나, 모두 보류할 수 있습니다. 보류된 작업은 승인 또는 거절할 때까지 설정 > 에이전트에서 기다립니다. - ### 조직별로 분리 조직 주소로는 그 조직의 회원에게만 접근할 수 있습니다. 다른 조직에 대한 접근은 모두 거부됩니다. - ### 모든 쓰기를 기록 모든 변경은 에이전트가 사용자를 대신해 한 것으로 기록되며, 설정 > 에이전트에서 언제든 에이전트 연결을 해제할 수 있습니다. - ### 지시가 아닌 데이터 채용 공고, 기업 페이지, 메시지는 따라야 할 지시가 아니라 읽을 데이터로 에이전트에 전달됩니다. 한도 ## 한도와 프로토콜 한도는 키마다 분 단위로 적용됩니다. 공개 주소는 네트워크 주소별로 제한됩니다. **공개 도구 호출** : 분당 30회 **읽기** : 분당 240회 **쓰기** : 분당 60회 **어시스턴트와의 채팅** : 분당 12회 **Cabinet 도구** : 분당 12회 **전송 방식** : Streamable HTTP, 스테이트리스 **프로토콜** : 2026-07-28 및 2025년 개정판 **결과 형식** : 채용 카드, JSON 텍스트, 구조화된 콘텐츠 자주 묻는 질문 ## MCP 서버에 관한 질문 **무료인가요?** 네. 공개 검색, 내 구직 활동, 조직 도구까지 모든 연결이 무료입니다. 사용량 한도 덕분에 모두가 빠르게 이용할 수 있습니다. **계정이 필요한가요?** 검색만 한다면 필요 없습니다. 공개 주소로는 로그인 없이 채용 공고와 기업을 검색할 수 있습니다. 내 프로필, 이력서, 지원을 관리하려면 무료 Metaintro 계정으로 로그인하세요. **어떤 클라이언트에서 쓸 수 있나요?** Streamable HTTP로 원격 MCP 서버를 지원하는 모든 클라이언트에서 쓸 수 있습니다. Claude, Claude Code, ChatGPT, Cursor, VS Code, Codex 등이 해당합니다. Claude와 ChatGPT는 채용 결과를 대화형 채용 카드로 보여 주고, 다른 클라이언트는 같은 결과를 JSON으로 받습니다. **나 대신 채용 공고에 지원해 주나요?** 아니요. 내가 한 지원을 기록해 관리 목록을 최신 상태로 유지할 뿐, 지원서를 제출하지는 않습니다. 케이스 매니저에게 보내는 메시지처럼 나를 대신해 보내는 것은 승인 설정을 따르며, 승인할 때까지 보류하도록 할 수 있습니다. **채용 API와는 무엇이 다른가요?** 채용 API는 직접 작성한 코드에서 쓰는 REST 엔드포인트로, 키 하나로 채용 공고를 분당 60회까지 검색합니다. MCP 서버는 AI 에이전트를 위해 만들어졌습니다. 에이전트가 스스로 도구를 찾아 쓰고, 로그인하면 채용 검색을 넘어 내 구직 활동까지 관리할 수 있습니다. 지금 시작하기 ## 한 줄로 에이전트에서 실시간 채용 공고 검색 지금 공개 주소를 추가하세요. 내 구직 활동을 맡기고 싶어지면 그때 로그인하세요. [계정 연결하기](/ko/settings/agents)[개발자 페이지로 돌아가기](/ko/developers) [내비게이션으로 돌아가기](#main-navigation)