Submission Reviewer MCP Server

The Husky Home Finder collects student submissions (apartment reviews, roommate interest, housing survey, and newsletter/waitlist sign ups.)

Currently, we would need to read each submission manually to catch duplicates, incomplete responses, and other bad submissions.

This MCP server adds AI review between submission and the database in order to classify the submissions, extract the data, summarize the information, and check for duplicates.

How Codex and GPT 5.6 were used

Codex was used as the main builder, building the MCP server (the tools, the typescript source (src), and the mock JSON data). I told Codex what I wanted each tool to do and then reviewed it, editing it based on the output.

GPT 5.6 is called, and powers two of the four tools: classifying submissions and extracting fields from the text reviews.

The other two tools (dedupe_check and summarize_batch) don't use AI calls, they are rule-based.

Related MCP server: Rentalot MCP Server

What it does

The server exposes exactly four tools:

The mock data deliberately includes ordinary valid submissions, likely duplicates, incomplete responses, and invalid values so the tools have useful results immediately.

Project layout

src/
  index.ts            MCP server and tool registration
  call-tool.ts        Small local MCP client for manual testing
  data.ts             Reads mock JSON data (replace this later for a database)
  analysis.ts         Duplicate detection and aggregate summaries
  openai-analysis.ts  Redacted GPT-5.6 classification and field extraction
  types.ts            Form data types
mock-data/            One JSON file for each form type

Setup

You need Node.js 20 or newer.

npm install
npm run build

Test a tool manually

The call command compiles the project, starts the server, calls one tool, prints its JSON result, and stops.

# Summarize a batch of housing surveys
npm run call -- summarize_batch --form housing_survey

# Find repeated roommate-interest submissions
npm run call -- dedupe_check --form roommate_interest

The AI tools require an API key. Copy .env.example to .env, add OPENAI_API_KEY, and use:

# Classify records for human data-quality review
npm run call:ai -- classify_submission --form roommate_interest

# Extract structured fields from apartment reviews
npm run call:ai -- extract_fields --limit 10

# Analyze one newly pasted apartment review instead of mock data
npm run call:ai -- extract_fields --text "The apartment is close to campus, but our unit had recurring plumbing problems."

# Classify one newly pasted housing-survey response
npm run call:ai -- classify_submission --form housing_survey --text "I live on campus, have a $1400 monthly budget, and want housing near the University District."

For pasted text, omit names, email addresses, phone numbers, and other direct identifiers. The server also redacts common email and phone-number patterns before making an AI request.

Form results also include a formOverview object so outside users understand what each form category represents:

Run as an MCP server

After building, start the standard-input/output server with:

npm start

For an MCP client configuration that uses the AI tools, start it with the environment file loaded:

npm run build
npm run start:ai

MCP uses standard output for protocol messages. The server sends status messages to standard error, so do not add ordinary console.log statements to src/index.ts.

An MCP client can register the compiled server with:

{
  "command": "node",
  "args": ["/absolute/path/to/submission-reviewer/dist/index.js"]
}

Privacy and MVP notes

This is a learning MVP, not production storage for real student data. The AI tools redact names, email addresses, and phone numbers before sending records to the provider. Classification and duplicate results are review aids, never automatic housing or roommate decisions.

Before collecting real submissions, add authentication and authorization, encrypted database storage and backups, consent and retention rules, rate limiting, audit logs, and a human review process.

Where to make changes later

• Add or change a form field: update src/types.ts, its JSON fixture, and summary or extraction logic.

• Use a database: replace loadSubmissions in src/data.ts; the tools can stay the same.

• Adjust duplicate matching: edit dedupeCheck in src/analysis.ts.