Neopat MCP

What neopat-mcp MCP server does

The neopat-mcp MCP server gives an MCP-compatible assistant access to a NeoPAT campus placement account. It can inspect available placement drives, search the portal's drive data, retrieve full drive details, evaluate eligibility, and expose the user's profile information for application preparation.

The server also supports the application workflow. Profile values such as marks, backlogs, registration details, contact information, and location can be used where the portal already has an answer. The assistant can identify unanswered questions and, in clients that support MCP elicitation, ask the user for the remaining information. Submitting an application requires a confirmation token created from a preview that the user has reviewed.

Interview information is available across drives the user has opted into, making the server useful for checking upcoming selection rounds in addition to finding openings.

How it works

The neopat-mcp MCP server runs as a standard stdio process. With uvx, a client can fetch and launch the published Python package without checking out the repository. It requires Python 3.11 or newer and uv.

Authentication can use either a NeoPAT email address and password or an auth_token copied from the portal's browser storage. The token method avoids storing a password but requires manual replacement after the token expires. Credential-based sign-in stores a session locally, uses refresh information to renew access, and does not repeatedly retry rejected credentials.

Tool responses publish output schemas, so clients can consume structured results for health checks, authentication state, drive records, eligibility results, and profile data. The health operation can be used to verify the connection and report token and drive information.

Setup and configuration

Install with uvx --from neopat-mcp neopat-mcp, then add that command to the MCP client's stdio configuration. Claude Desktop also has a packaged .mcpb release that can be opened directly. Source installation is available with uv sync, after which the server can be launched through the project virtual environment.

For automatic sign-in, configure NEOPAT_EMAIL and NEOPAT_PASSWORD. Alternatively, set NEOPAT_TOKEN to a browser-copied token; it takes precedence when both authentication methods are present. The default API root is https://api.neopat.ai/api/v1.

Request pacing defaults to a 700-millisecond minimum interval. Confirmation tokens last 600 seconds by default. NEOPAT_HOME can relocate the directory holding the cached session. When using a checkout, credentials may be placed in .env.local, which should remain excluded from version control.

Tools and capabilities

The neopat-mcp MCP server includes tools for:

• Checking portal connectivity, token validity, expiry, and drive counts.
• Inspecting authentication mode, signing in, signing out, and checking token lifetime.
• Listing drives with eligibility, open-deadline, already-applied, and search filters.
• Searching through the portal's own drive search, which covers more fields.
• Opening a drive's complete record, including its application questions.
• Checking the portal's eligibility decision and its explanation.
• Reading the user's profile and commonly needed application answers.
• Preparing and submitting applications through a preview-and-confirm flow.
• Viewing upcoming interview rounds for opted-in drives.

Application submission is deliberately two-step: a preview must produce a confirmation token, and that token must be used before the configured confirmation lifetime ends. The server does not treat a conversational request alone as permission to file an application.