Neopat MCP Server

neopat-mcp

An MCP server for the NeoPAT campus placement portal. It lets an AI assistant browse your drives, fill in each company's application form from your profile, and file applications — with your explicit confirmation every time.

Features

• Stays signed in — signs in with your credentials and renews the session itself, or works from a token you paste.
• Browse and search drives — filter by eligibility, open deadlines, or whether you have already applied.
• Answers filled from your profile — marks, backlogs, registration number, contact details and location are taken from the portal's own record of you, and each one reports where it came from.
• Asks you for the rest — on clients that support elicitation, the server prompts you directly for answers it cannot infer.
• Two-step applications — nothing is submitted without a confirmation token issued by a preview you have seen.
• Interview schedule — upcoming rounds across every drive you opted into.
• Typed responses — every tool publishes an output schema.

Requirements

• Python 3.11 or newer
• uv
• An account on a NeoPAT placement portal

Installation

Claude Desktop — one click

Download neopat-mcp.mcpb from the latest release and open it. Claude Desktop installs it and asks for your credentials, which it keeps in your operating system's keychain rather than in a file.

Everything else

No clone or checkout needed — uvx fetches and runs it:

uvx --from neopat-mcp neopat-mcp

Add it to any client with one of the configurations below.

git clone https://github.com/Udhay-Adithya/neopat-mcp.git
cd neopat-mcp
uv sync

Then point your client at .venv/bin/python -m neopat_mcp.server.

Configuration

Credentials go in your client's env block (shown under Usage), or in a .env.local file when running from a checkout.

There are two ways to authenticate. Pick one.

Sign in (recommended)

NEOPAT_EMAIL="you@example.com"
NEOPAT_PASSWORD="your-portal-password"

The server signs in once and caches the session in .neopat-session.json (gitignored, mode 0600). Access tokens last 24 hours; a refresh token renews them automatically, so your password is used once and the session keeps itself alive after that.

Repeated rejections stop further attempts rather than retrying in a loop — that is how accounts get locked. Fix the credentials and call sign_in.

Paste a token

NEOPAT_TOKEN="paste-auth_token-here"

From DevTools → Application → Local Storage → auth_token. No password is stored, but the token expires after 24 hours and cannot renew itself, so you replace it by hand. It takes precedence when both are configured.

This bookmarklet copies the current token in one click:

javascript:(()=>{navigator.clipboard.writeText(localStorage.getItem('auth_token'));alert('Token copied');})()

All settings

The session is cached under your user data directory — ~/.local/share/neopat-mcp on Linux, ~/Library/Application Support/neopat-mcp on macOS, %LOCALAPPDATA% on Windows — with permissions 0600. Set NEOPAT_HOME to move it.

When running from a checkout, .env.local is gitignored. Keep it that way: it holds a live credential.

Usage

GitHub does not make badge links clickable in every view; the configurations below are the same thing written out. Replace the placeholder credentials with your own.

Every client runs the same command, so nothing below needs a checkout.

claude mcp add neopat \
  --env NEOPAT_EMAIL=you@example.com \
  --env NEOPAT_PASSWORD=your-password \
  -- uvx --from neopat-mcp neopat-mcp

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{
  "mcpServers": {
    "neopat": {
      "command": "uvx",
      "args": ["--from", "neopat-mcp", "neopat-mcp"],
      "env": {
        "NEOPAT_EMAIL": "you@example.com",
        "NEOPAT_PASSWORD": "your-password"
      }
    }
  }
}

.cursor/mcp.json, or ~/.cursor/mcp.json for all projects:

{
  "mcpServers": {
    "neopat": {
      "command": "uvx",
      "args": ["--from", "neopat-mcp", "neopat-mcp"],
      "env": {
        "NEOPAT_EMAIL": "you@example.com",
        "NEOPAT_PASSWORD": "your-password"
      }
    }
  }
}

.vscode/mcp.json:

{
  "servers": {
    "neopat": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "neopat-mcp", "neopat-mcp"],
      "env": {
        "NEOPAT_EMAIL": "you@example.com",
        "NEOPAT_PASSWORD": "your-password"
      }
    }
  }
}

~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "neopat": {
      "command": "uvx",
      "args": ["--from", "neopat-mcp", "neopat-mcp"],
      "env": {
        "NEOPAT_EMAIL": "you@example.com",
        "NEOPAT_PASSWORD": "your-password"
      }
    }
  }
}

{
  "context_servers": {
    "neopat": {
      "command": {
        "path": "uvx",
        "args": ["--from", "neopat-mcp", "neopat-mcp"],
        "env": {
          "NEOPAT_EMAIL": "you@example.com",
          "NEOPAT_PASSWORD": "your-password"
        }
      }
    }
  }
}

cline_mcp_settings.json:

{
  "mcpServers": {
    "neopat": {
      "command": "uvx",
      "args": ["--from", "neopat-mcp", "neopat-mcp"],
      "env": {
        "NEOPAT_EMAIL": "you@example.com",
        "NEOPAT_PASSWORD": "your-password"
      },
      "disabled": false
    }
  }
}

A standard stdio server:

uvx --from neopat-mcp neopat-mcp

with NEOPAT_EMAIL and NEOPAT_PASSWORD in the environment.

Ask your assistant to run health to confirm the connection.

Tools

Reading

Writing

Prompts

Resources

How applying works

Applying takes two calls, and the second one cannot invent anything.

get_drive  ->  preview_application  ->  [you approve]  ->  apply_to_drive

preview_application reads the drive's questions, fills in what your profile answers, asks you for the rest, and validates everything. It returns a single-use confirmation token bound to that drive and to a hash of the exact request body.

apply_to_drive takes no payload. It can only replay a body that was already previewed. An assistant cannot apply as a side effect of browsing, cannot apply to a drive other than the one you were shown, and cannot alter an answer between your approval and the request.

No token is issued at all when something is wrong — you are ineligible, the deadline has passed, a mandatory question is unanswered, an answer is not one of the permitted options, or the portal already records you as applied.

Answers are keyed by question id, never by question text:

{
  "drive_id": "...",
  "answers": { "8af2166d-8202-4932-b5a7-f3a01c80d7e9": "Development" }
}

Free-text questions about marks, backlogs, contact details and location are filled from your profile automatically and reported in auto_answered. Multiple-choice questions are never answered for you — picking an option is a preference, not a lookup.

Development

uv sync --all-groups
.venv/bin/python -m pytest

Tests run against a stubbed portal and never contact the real one.

src/neopat_mcp/
├── schemas.py       Typed models for every response
├── parsing.py       Portal payloads -> schemas
├── applications.py  Question answering, validation, write payloads
├── client.py        HTTP: auth, rate limiting, retries, pagination
├── confirm.py       Single-use confirmation tokens
├── config.py        Settings and the hot-reloaded token
└── server.py        MCP tools, prompts and resources

docs/api-notes.md documents the portal's API behaviour, including several endpoints that fail in misleading ways.

Disclaimer

Unofficial, and not affiliated with or endorsed by NeoPAT. It automates actions you can already perform yourself, on your own account, with your own credentials. Opting into a drive files a real application with a real company — check your institution's placement policy before automating anything, and read every preview before confirming it.

License

MIT