RequirementsHub Resident MCP

The fastest way to run Resident. No connector setup — Claude runs the skill locally and your document content never leaves your machine.

1. In Claude, go to Settings → Capabilities and enable Code execution and file creation.
2. Go to Customize → Skills → “+” → Create skill and upload the Resident skill package (download below).
3. Toggle it on, start a conversation, and share your requirements documents.
4. When you’re ready to run a scored analysis, paste your license key directly into the chat message. Claude uses it only for that conversation and never stores or repeats it back — you’ll do this once per new conversation, not once ever.

Endpoint

https://requirementshub.ai/api/public/resident/mcp

Speaks MCP Streamable HTTP (JSON-RPC 2.0 over POST). Stateless — clients carry the session token themselves across calls.

Authentication

Resident uses bearer license-key / session-token authentication — it does not use the Supabase OAuth flow shown in the platform's Agent Integrations panel for the main SaaS MCP connector. Call resident_start_session with your license key to mint a short-lived session token, then send that token as Authorization: Bearer <token> and in the token field of every subsequent tool input (the mismatch guard rejects mixed-identity calls).

Setup

1. Obtain a license key — see pricing. (Standalone Resident subscription, or included with RequirementsHub Pro.)
2. Register the endpoint above in your MCP client (Claude custom connector, Copilot agent, ChatGPT app, or any MCP-compatible runtime).
3. Call resident_start_session with the license key. Store the returned token client-side.
4. On every following call, send the token as an Authorization: Bearer header AND in the tool input's token field.

Pricing

Standalone Resident includes the Resident license only — Pro app access is not included.

Available tools

• resident_start_session

  Exchange a RequirementsHub Resident license key for a short-lived session token used as the bearer credential on subsequent Resident tool calls.

• resident_get_packs

  Fetch the watermarked keyword, instruction, and prompt packs for a given domain context. Used by the Resident client to run local extraction and scoring.

• resident_get_templates

  Fetch versioned template assets (extraction, executive_summary, test_cases, rtm) for producing Resident deliverables locally.

• resident_submit_analysis

  Score an anonymized skeleton payload (no free text) with the RequirementsHub rules engine and return dimension scores, detected stage, and findings.

• resident_get_catalog

  Return the finding catalog and pack/engine version metadata so clients can align local rendering with the current Resident release.