MCP App Store
by KeenEthics
Terac icon

Terac MCP Server for Claude and ChatGPT

By Terac

Overview

Terac connects Claude to vetted human experts for research and expert labor. Define what you need done and who should do it; Terac handles recruiting, screening, task delivery, quality grading, and expert payouts end to end.

How to connect

  1. Claude: Open the Terac listing in the Claude connectors directory and choose Connect. Claude listing Terac exposes 23 tools here.
  2. ChatGPT: Open the Terac listing in the ChatGPT app directory and choose Connect. ChatGPT listing Terac exposes 26 tools here.

Tools

terac_approve_submission

ChatGPT
Approve a submission that is AWAITING_REVIEW. Approving pays the expert and marks the submission as accepted toward the opportunity's target count. On an hourly or per_task opportunity it accepts the reviewed work only: the expert stays in_progress on the project, and the response says so. Only submissions in AWAITING_REVIEW can be approved, calling on any other state returns a CONFLICT error. Use terac_get_submissions to find submissions awaiting your review. Review the submission's deliverables against the success/failure criteria you wrote in the task description before approving. Approval is how experts get paid, so it commits funds.

terac_create_opportunity

ChatGPT
Create a DRAFT opportunity directly, with full control over tasks, structured targeting filters, screening questions, and quotas. Nothing is charged and no recruitment starts until you call terac_launch_draft_opportunity. Use this draft-first path when you need precise, structured targeting rather than a free-text panel description. Before you call this tool terac_get_context's operating guide sorts every study value into ASK, PROPOSE-and-CONFIRM, and ASSUME. This tool is where that sorting binds: do not call it while an ASK value is still unknown. Do not dump every missing value into one message. A numbered list of four is a form, and a form gets skimmed, which is how the answer that mattered gets a careless number. How many to send at once is your judgement, so decide it like this: ask only what you genuinely cannot proceed without, lead with the one that changes the study most, and add a second only when it is answered in the same breath (count and budget, country and language). Anything whose answer would change what you ask next goes in a later message, alone. One good question is a better opener than three adequate ones. A free draft is not a way around this either, because a guessed participant count or an empty audience reads as a decision once it is in the builder. Creating a project with terac_create_project meanwhile is fine; creating an opportunity is not. Everything in the PROPOSE bucket is yours to fill in with your best value. Do not hand the customer a blank form: choose the method, the task structure, the screener wording and the quotas, then surface them for confirmation at hand-off. How many opportunities to create Default to ONE opportunity. Split into separate opportunities only when a segment is a DISTINCT DELIVERABLE, it needs its own sample target, its own language/localization, or independent launch/pause/pricing. In practice that usually means splitting by market when each market has its own quota and localized screener (US, UK, and Germany at 20 interviews each with a localized screener = three). Do NOT split when the segments are one eligible pool that shares a sample, language, and task. Multiple countries recruited as a single pool (e.g. English-speaking experts across US/UK/Canada with one combined sample) go in ONE opportunity via a multi-value country filter; likewise multiple roles, audiences, or seniorities in the same market belong in one opportunity via filters + screening_questions. When unsure, make one. If you have a priced feasibility request (see terac_request_feasibility), pass its id as feasibility_request_id to price this opportunity from that confirmed CPI instead of an autonomous estimate, and Terac skips the estimate and LLM steps. The request stays RESPONDED until the draft actually launches, and only then reads WON, so a request you read back as still RESPONDED after this call has not failed to attach; an abandoned draft must not win the deal. Key fields: - title: human-facing opportunity name. - description: what the opportunity is about, shown to participants. The field and the draft both accept up to 8000 characters, but the study builder a researcher edits it in is capped at 280, so anything longer has to be cut down by hand before they can touch it there. Lead with what matters and keep it inside 280 characters. - project_id: project to file this under (from terac_list_projects / terac_create_project). - num_participants: number of completed submissions you need. - business_type: 'b2c' or 'b2b'. - tasks: ordered steps each expert performs. Each task needs sequence, task_type (interview | file_upload | activity) and review_type (auto_approve | manual_review | self_report). duration_minutes is required except on file_upload, which carries no time estimate. Pick task_type by where the answer lands: interview when you have a page they work and submit on, file_upload when the deliverable is a file, and activity ONLY when you want nothing back, because it collects nothing. Do not reach for activity just because the work is not literally an interview. With no page yet…

terac_create_project

ChatGPT
Create a project to group related opportunities. Projects keep an organization's work organized; pass the returned project ID as project_id to terac_create_opportunity.

terac_decline_applicant

ChatGPT
Decline an applicant from terac_get_applicants. They are not invited, never reach the task, and the submission becomes screened_out. This ends that expert's participation in the opportunity and tells them they were not selected, so it is not the way to defer a decision: leaving them in the queue is. A reason is optional on the wire and recorded on the submission's history for your own team; give one, because a decline with no reason leaves nothing for a later question to be answered from. Returns CONFLICT when the applicant is not awaiting a decision, which includes one already decided.

terac_delete_opportunity

ChatGPT
Delete a draft opportunity. Only opportunities in DRAFT or CREATING status can be deleted, to end a launched opportunity use terac_stop_opportunity instead.

terac_get_applicants

ChatGPT
List the applicants waiting on a decision before they can start the task. An opportunity on customer_screening_review=manual_review sends every qualified applicant here; one on auto_invite still sends the individuals a screener answer graded review, so poll it either way. They are absent from terac_get_submissions and terac_get_submission returns NOT_FOUND for them: they have passed the screener but hold no submission status until you decide. Each row carries the screening_answers that decision is made from. Resolve one with terac_invite_applicant or terac_decline_applicant; either way they leave this queue and appear in terac_get_submissions. Nothing announces an arrival, so poll on the same cadence as terac_get_submissions, and report the queue depth rather than sitting on it: an applicant nobody decides on is an expert waiting indefinitely.

terac_get_context

ChatGPT
IMPORTANT: Call this tool FIRST before using any other Terac tool. What is Terac? Terac is the human labor MCP. When your agent needs a real human to do something, interview an expert, test a product, label data, verify a claim, grade a deliverable, or provide domain expertise, Terac finds the right person, screens them, manages the task, verifies completion, and handles payment. Think of it as the bridge between AI agents and the real world of human skill and opinion. Terac owns and operates a vetted expert panel spanning every industry and geography. You define WHAT you need done and WHO should do it. Terac handles the rest: recruiting, screening, task delivery, quality grading, and payout. What This Tool Returns A markdown summary of your authenticated organization including: - Organization identity (name, slug, ID) - Current balance (calculated from the ledger, reflects the environment your API key is connected to) - All projects in the organization - Opportunity counts by status - Dashboard URLs, absolute links into the researcher dashboard where a human reviews and controls this work: the organization's home, its opportunities, its drafts, its feasibility requests, where it tops up its balance, and where it manages API keys. Every project row carries its own URL too. Hand these to the customer instead of a bare id; they almost certainly have the dashboard open. Use them exactly as returned, the host and the route shape both come from the response, never from a pattern you assemble. - Organization Policies, org-specific instructions. If present, these are non-negotiable constraints set by the org admin. You MUST embed them into every task and panel specification you create. These may include required consent language, mandatory demographic quotas, geographic restrictions, budget thresholds, prohibited topics, or approval workflows. No org policies in the response means there are none to apply: proceed, and do NOT ask the customer for guidelines, consent language, privacy or compliance requirements. An org admin sets those, not them. Core Workflow Every engagement follows this sequence: 1. Call terac_get_context (this tool) to understand your org, balance, and policies. 2. Align with the user. Understand what they want to learn before you build. The operating guide in this tool's result sorts every study value into what you ask for, what you propose and then get confirmed, and what you simply assume. Read terac_create_opportunity's own description before you build with it. 3. Price and build the draft. Pick one of the paths in "Ways to Launch" below: request feasibility (human-confirmed price) or build a draft with explicit targeting. Either way you end up with a DRAFT, which costs nothing and starts no recruitment. 4. Hand the draft to the customer. Give them the draft's links.dashboard.draft_editor URL and the confirmation block terac_create_opportunity specifies, so they can review the whole setup. 5. Launch once they confirm. Launching commits real money and begins recruitment. A draft you built with terac_create_opportunity carries its own screener and materials already, so it goes straight to ACTIVE with no preparation phase in between. 6. Confirm it is recruiting. The launch response already carries the new status, so there is nothing to wait out; read progress from terac_get_opportunity from here on. 7. Monitor submissions (terac_get_submissions). As experts complete the task, submissions appear. Check periodically, recruitment is asynchronous and can take minutes to days depending on panel difficulty. 8. Review results. Read each submission's screening answers, qualification status, and task deliverables, then approve (terac_approve_submission) or reject (terac_reject_submission) each submission that is AWAITING_REVIEW. Approving pays the expert; rejecting requires a reason. Ways to Launch Two ways to price and build an opportunity. Both end at a draft you hand over, and both commit real money only at the launch the customer asks for; they differ in how the price i…

terac_get_feasibility_request

ChatGPT
Retrieve one of your feasibility requests by ID. This is how you learn the price: read status, and read costPerParticipant, which is null until the request is priced. Read the status before you read the price Five values, and only one of them means you have a price: - RECEIVED: not priced yet. costPerParticipant is null and there is no price to report. - RESPONDED: priced. costPerParticipant is the confirmed all-in CPI per participant. Create the opportunity with terac_create_opportunity (pass feasibility_request_id) and launch it with terac_launch_draft_opportunity. - WON: this request already priced a study that launched. It is spent; do not attach it to a new draft. - LOST or NOT_PURSUED: closed without a usable price. Both are TERMINAL. Nothing further will arrive, so stop polling. On a terminal status the response carries no reason, so you do not know whether the audience was unsourceable, the timeline impossible, or the request simply closed. Tell the customer it came back without a price, do not invent why, and offer the next real move: build the draft for an estimated price, re-scope the audience and request feasibility again, or ask us via the dashboard_url. Polling cadence Poll once as soon as you have the id, before waiting at all: many requests are already priced by then, and sleeping first only adds that delay to the customer's wait. If it is still RECEIVED, poll every couple of minutes for the first fifteen, then back off to every fifteen to thirty. Past that a person is pricing it and it may take hours; polling harder will not help and there is no webhook to wait on. If your runtime cannot stay open that long, say so, hand over the dashboard_url so the customer can watch the price land, and offer to pick it back up. Do not fill the gap with a number.

terac_get_filter_options

ChatGPT
List the allowed values for a single filter (e.g. the list of countries, industries, or seniorities). Results are paginated and searchable. Geographic filters cascade: for states pass country_id, and for cities pass country_id (and optionally state_id). Use the returned option ids as filter values when building an opportunity's filters.

terac_get_opportunity

ChatGPT
Get full details for an opportunity: id, title, status, num_participants (your target), estimated_duration_minutes, pricing, filters, screening_questions (with qualify_logic), tasks (with participant_url_template), and device_types. Once launched it also includes submission_stats (total / in_progress / awaiting_review / approved / rejected) for at-a-glance progress, quota_progress (per-segment approvals when you set quotas, each carrying the target's type so you can tell whether current approaching count means a cap is about to close or a floor is about to be met), and links to related endpoints. links.dashboard carries this study's pages in the researcher dashboard. When you report on an opportunity, give the customer the URL that matches what you are telling them, draft_editor for a draft they still have to review, submissions for progress on a launched one, rather than only its id. Reading a Screener Back screening_questions comes back in the shape terac_create_opportunity accepts, so you can send it straight back on an update. Two fields read back normalized rather than verbatim, and neither is an error to "fix": - qualify_logic on a single-select (pick "one", which is also how a yes/no question reads back) is always "must" for any qualifying answer, because "may", "must" and "must_one_of" mean the same thing when only one answer can be picked. A "may" you sent reading back as "must" is what is stored; rewriting it to "may" will not make the question filter. Use "reject" to screen out, or pick "any" for per-answer logic. - A quota target stored without a type reads back as "exact", because that is how enforcement treats an untyped quota. That is about quotas stored that way (older or dashboard-authored ones), not about what you sent: a type you write is stored and reads back unchanged, and omitting it on write stores "minimum". Polling for Status Use this tool to poll for status transitions. Key patterns: - After launching: nothing to poll for. A draft you launch is already active in the launch response. - While ACTIVE: poll every 5-15 minutes and read submission_stats to track progress vs num_participants. For large or niche audiences, poll every 30-60 minutes. - The opportunity continues running on Terac's side regardless of whether you are polling. - If your runtime has idle limits, inform the user that results will take time and offer to check back. Opportunity Lifecycle State Machine DRAFT --> ACTIVE --> FULFILLED --> COMPLETED | ^ | | +---------+ (FULFILLED auto-reopens to ACTIVE if approvals drop below target) | |---> PAUSED --> ACTIVE (via terac_resume_opportunity) | +---> STOPPED (permanent, irreversible) - DRAFT: built and priced; nothing charged and nobody recruited until you launch it. An opportunity Terac is still preparing from a REST quote also reads as draft; status has no separate value for it. - ACTIVE: Recruitment is running. Submissions appear over time. - PAUSED: Recruitment suspended. In-progress submissions unaffected. - FULFILLED: Target submission count reached; in a short grace window before COMPLETED. New applicants are blocked. Terac auto-reopens it to ACTIVE if approved submissions drop below target (the self-healing quota). It cannot be paused or stopped. - COMPLETED: All target submissions delivered. - STOPPED: Permanently ended. Unused budget refunded. Cannot be restarted. Outside that flow, and none can be launched, edited or deleted (status reads each in lowercase): - PRE_RECRUITING: Taking applicants ahead of a launch set up in the dashboard, charged only when it launches there. terac_stop_opportunity is the only tool that applies. - EXPIRED: Its recruitment window closed before the target was reached. Ended. - CANCELLED: Ended by Terac, unused budget refunded. - FAILED: Its launch from a REST quote never finished, and no tool can change it. Create a new opportunity; pricing shows anything that was charged. Valid transitions: - terac_pause_opportunity: ACTIVE -> PAUSED - terac_resume_opportunity: PAUSED -> ACTIVE - terac_stop_opportunity: ACTIVE, PAUSED, or PRE_RECRUITING -…

terac_get_project

ChatGPT
Get a single project's details, including how many opportunities it contains.

terac_get_submission

ChatGPT
Get one submission's detail: id, status, participant_id, created_at, updated_at, plus: - screening_answers: the expert's answers to your screening questions (key, question, answer[]). Empty when the opportunity has no screeners (e.g. a draft created without screening_questions). - tasks: per-task progress (sequence, task_type, status) so you can see how far they got. Status uses the same seven values as terac_get_submissions, which documents the mapping. Calling on a not-yet-surfaced submission returns NOT_FOUND.

terac_get_submissions

ChatGPT
List the submissions for an opportunity. Use this to monitor experts as they move through the task. What Is Returned A paginated list. Each item is a lightweight summary: id, status, participant_id, created_at, updated_at. Use pagination.next_cursor to page, and the optional status filter to narrow. Every row carries screening_outcome and screening_answers; call terac_get_submission with an id only when you also need its per-task progress. dashboard_url is where a human reviews these same submissions in the researcher dashboard (null while the opportunity is still a draft). Hand it over whenever you report progress or flag work awaiting review. Submission Statuses Surfaced Seven, in lifecycle order: - screen_passed: qualified, has not started the task - screened_out: answered the screener and did not qualify, so never reached the task - in_progress: actively working the task - awaiting_review: task completed, pending your review (for manual_review tasks) - approved: accepted (the expert is paid) - rejected: did the work and it was not accepted, or was taken off an hourly or per-task project part way through - abandoned: stopped part-way without being screened out screened_out applicants count toward nothing on your target, but their answers are why: filter status=screened_out and read screening_answers, which carries the per-answer verdict. For rates rather than individuals, read screening_stats on terac_get_opportunity. Applicants still in the screener are NOT surfaced, in either the list or by id, and neither is one that has not started it, so terac_get_submission on one returns NOT_FOUND. You see such an applicant once they reach screened_out or screen_passed. One group of them is readable though, and is the group somebody has to act on: an applicant who has passed the screener and is waiting on a decision appears in terac_get_applicants, with the answers that decision is made from. They enter this list once invited or declined. Counts vs. This List For aggregate progress (total / in_progress / awaiting_review / approved / rejected) read submission_stats on terac_get_opportunity instead of counting this list by hand. It covers those five statuses only, so screener and abandoned counts still come from this list or from screening_stats. Polling Cadence Recruitment is asynchronous, so poll periodically: - Every 5-15 minutes for active opportunities with common audience profiles - Every 30-60 minutes for large quotas or niche audiences - Don't poll too aggressively, human labor is slower than API calls. The opportunity keeps running on Terac's side whether or not you poll.

terac_invite_applicant

ChatGPT
Invite an applicant from terac_get_applicants. Their tasks are materialized and they are notified, so the expert can start work; the submission becomes screen_passed and counts toward the target. Decide from the row's screening_answers, against the criteria the screener was written to test. Whose judgement this is matters: on a close call put the answers to the customer rather than inventing a standard of your own. Returns CONFLICT when the applicant is not awaiting a decision, including one already decided; re-read terac_get_applicants rather than retrying.

terac_launch_draft_opportunity

ChatGPT
Launch a DRAFT opportunity that was created via terac_create_opportunity. This commits real money and begins recruitment. Because this spends the customer's budget and is not silently reversible, only launch when the customer has EXPLICITLY asked to launch, go live, or start recruiting. Setting a study up, quoting feasibility, or confirming targeting does NOT imply launch: leave it as a draft and let the customer review pricing (via terac_get_opportunity) and confirm first. When in doubt, do not launch. The explicit ask comes after a review, so give them something to review: hand over the draft's links.dashboard.draft_editor URL, wait for them to come back, and only then call this. That approval has to arrive in a later turn than the confirmation block terac_create_opportunity specifies, and it has to be an answer to it. A request that already said 'launch' before the draft existed approves nothing the customer has not seen yet, and neither does silence after a summary; both leave the participant count, the targeting, the duration and the screener unconfirmed, which is the whole reason for the block. Only an opportunity whose status reads draft can be launched; anything else returns a CONFLICT error. The launched opportunity comes back in the response, already active, so there is no preparation phase to poll through. No study launches unscreened by accident. screening_questions is optional at creation, but a draft with no screener, or one whose screener nobody can pass, is REFUSED here rather than launched: applicants would otherwise reach paid work with nobody filtered out. The error names the problem; write the criteria the task calls for, repair it with terac_update_opportunity's screening_questions, and show the customer what you wrote before you try this again. Only when the customer says no screener is needed, and the refusal says their organization can launch without one, send without_screener: true. Unless Terac runs its AI screening interview on the opportunity, the tasks that deliver the work have to be review_type manual_review first, because everyone who matches the filters goes straight to the task and nobody is paid until their submission is approved. Never send it just to get past the refusal.

terac_list_feasibility_requests

ChatGPT
List your organization's feasibility requests, newest first. Optionally filter by status; terac_get_feasibility_request documents what each status means.

terac_list_filters

ChatGPT
List the structured filters available for precise audience targeting (demographic, geographic, and professional attributes such as age, country, industry, seniority, and more). Each filter has a slug, a type (integer, single_select, multi_select, reference), and the operators it supports. Filters whose values come from a controlled vocabulary expose an options_url, use terac_get_filter_options to fetch the allowed values. Use these filters in the filters field of terac_create_opportunity for hard, structured targeting. This is more precise than a free-text panel description because it maps to verified panel attributes.

terac_list_opportunities

ChatGPT
List opportunities in your organization with status, pricing, and timeline for each. Returns a paginated list. Use pagination.next_cursor from the response to fetch subsequent pages. Supports filtering by project and/or by a single status. Only non-deleted opportunities are returned.

terac_list_projects

ChatGPT
List your organization's projects. Projects group related opportunities together. terac_create_opportunity requires a project_id: pass the id of one of these projects, or create one with terac_create_project first. Returns one page of projects, sorted by name. When pagination.has_more is true there are more: call again with cursor set to pagination.next_cursor, and repeat until has_more is false. Only STANDARD visibility projects are returned. INTERNAL projects are hidden by design.

terac_pause_opportunity

ChatGPT
Pause an active opportunity. All recruitment is suspended immediately. Existing in-progress submissions are unaffected, experts who have already started the task can still complete it. Use terac_resume_opportunity to restart recruitment. Only valid when opportunity status is ACTIVE. Calling on a non-ACTIVE opportunity returns a CONFLICT error. Pausing is free and instant. Encourage the user to use pause/resume proactively rather than waiting and hoping, for example, 'pause everything while we review initial results' is a perfectly normal workflow.

terac_reject_submission

ChatGPT
Reject a submission that is AWAITING_REVIEW. The expert is not paid for a rejected submission and Terac may recruit a replacement to keep filling the opportunity's target count. Only submissions in AWAITING_REVIEW can be rejected, calling on any other state returns a CONFLICT error. Strongly recommended: provide a rejection_category and a clear rejection_reason. Both are optional on the wire, but a rejection with no reason leaves no audit trail for the non-payment. When you give a reason, reference the specific success/failure criteria from the task description that the submission failed to meet; this also improves future grading. rejection_category values: - low_quality: effort is present but the work is poor or shallow - failed_instructions: did not follow the steps or format you specified - incomplete: missing required deliverables or stopped early - suspicious_patterns: signs of fraud, AI-generated answers, or duplicate/bot activity - other: anything else (always pair with a detailed rejection_reason)

terac_request_feasibility

ChatGPT
Submit a feasibility request: can we source a panel for this task, and at what CPI. Returns immediately with status RECEIVED and costPerParticipant null. The price is set out of band by one of two routes you cannot choose or observe: some requests are priced automatically in under a minute, the rest by a person. So treat a fast answer as normal, and do not promise the customer a turnaround. Poll terac_get_feasibility_request, which carries the cadence and the statuses; once priced, create the opportunity with terac_create_opportunity (passing feasibility_request_id) and launch it. Only the brief is priced, so the draft has to match it Whoever prices this sees taskDescription, panelDescription, and the count and timeline. Nothing else: the filters, screening questions and tasks you build later do not exist yet. The CPI you get back prices the brief you wrote and is then honored against whatever draft you attach it to. So write the brief fully, because a brief missing the seniority or the market is priced for a cheaper audience than the one you then try to recruit, and the study underfills at a rate nobody will take. And if the customer changes the count, audience or task after the price lands, that CPI no longer prices what you are about to launch: say so and request feasibility again. Never fill in the price yourself costPerParticipant is the only price this flow produces; until it is set there is no price. While a request is unpriced, do not name a figure, a range, a total, or a comparison to what a study like this usually costs, in prose or in a table. Your own sense of what research costs is not the quote, another study's CPI is not this quote, and the autonomous estimate terac_create_opportunity returns without a feasibility_request_id is a different number by a different method, so it is not this quote either. A customer told a number remembers it as the price, and the reason to ask is that our estimate may be wrong. Saying you do not have it yet is the true answer. The response carries dashboard_url, the feasibility page in the researcher dashboard where this request and its quote show up. Give it to the customer while you wait, so they can watch the price land.

terac_resume_opportunity

ChatGPT
Resume a paused opportunity. Recruitment restarts automatically and Terac continues filling remaining submission slots. Only valid when opportunity status is PAUSED. Calling on a non-PAUSED opportunity returns a CONFLICT error. Resuming is free and instant.

terac_stop_opportunity

ChatGPT
Permanently stop an opportunity. This action is IRREVERSIBLE. All pending invitations are rescinded, unused budget is refunded to your organization, and recruitment cannot be restarted. If you might want to continue later, use terac_pause_opportunity instead. Valid when opportunity status is ACTIVE, PAUSED, or PRE_RECRUITING. Calling on an opportunity in any other status returns a CONFLICT error. If the research direction changes, stop the current opportunity and launch a new one with different specifications rather than trying to modify the existing one.

terac_update_opportunity

ChatGPT
Edit a DRAFT opportunity in place: its copy (title, internal title, description), participant count, business type, allowed devices, recruitment window, tasks, targeting filters, and screening questions + quotas. Send only the fields you are changing; anything you omit is left exactly as it is. Every list field REPLACES the stored list wholesale, tasks, filters, screening_questions and quotas are never merged. So to add, remove or reorder one item, first read the opportunity with terac_get_opportunity, change that item, and send the FULL list back; sending one task where two exist deletes the other. quotas only apply alongside screening_questions in the same call. Because of that, an empty filters array is the same act as creating an opportunity without any, and it is refused the same way: send it only alongside unrestricted_audience: true. That flag is about what THIS call does to the audience, so it is also refused on a call that leaves filters alone, and refused alongside a non-empty filters list. Launched opportunities still cannot be edited, a non-draft returns a CONFLICT error. To change a live opportunity, stop it and create a new one.

terac_update_project

ChatGPT
Rename an existing project.

terac_approve_submission

Claude

terac_create_opportunity

Claude

terac_create_project

Claude

terac_delete_opportunity

Claude

terac_get_context

Claude

terac_get_feasibility_request

Claude

terac_get_filter_options

Claude

terac_get_opportunity

Claude

terac_get_project

Claude

terac_get_submission

Claude

terac_get_submissions

Claude

terac_launch_draft_opportunity

Claude

terac_list_feasibility_requests

Claude

terac_list_filters

Claude

terac_list_opportunities

Claude

terac_list_projects

Claude

terac_pause_opportunity

Claude

terac_reject_submission

Claude

terac_request_feasibility

Claude

terac_resume_opportunity

Claude

terac_stop_opportunity

Claude

terac_update_opportunity

Claude

terac_update_project

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/terac"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/terac)