HIPAA Guardian MCP Server

Implementation Reference

• server.ts:167-184 (registration)

  Complete registration of the 'getDeveloperConsiderations' MCP tool, including description, empty input schema using Zod, and inline async handler that returns a markdown/text content block sourced from the global hipaaData object.
  /** * Tool for understanding developer-specific architectural decisions. */ server.tool( 'getDeveloperConsiderations', { description: 'Provides guidance on key developer decisions, including the cloud Shared Responsibility Model and a framework for "Build vs. Outsource" choices.', schema: z.object({}), }, async () => { return { content: [{ type: 'text', text: hipaaData['developer_considerations'] }] }; } );
• server.ts:176-183 (handler)

  The inline handler function executing the tool logic: fetches 'developer_considerations' from hipaaData and formats it as MCP content response.
  async () => { return { content: [{ type: 'text', text: hipaaData['developer_considerations'] }] }; }
• server.ts:8-18 (helper)

  Loads the hipaaData JSON object from 'hipaa-content.json' at startup, providing the data source ('developer_considerations') used by the tool handler.
  const knowledgeBasePath = path.join(process.cwd(), 'hipaa-content.json'); let hipaaData; try { hipaaData = JSON.parse(fs.readFileSync(knowledgeBasePath, 'utf-8')); console.log('✅ HIPAA knowledge base loaded successfully'); } catch (error) { console.error(`FATAL ERROR: Could not load knowledge base from ${knowledgeBasePath}.`); console.error('Please ensure the hipaa-content.json file exists in the same directory.'); console.error('Error details:', error); process.exit(1); // Exit if the core data is missing }
• server.ts:172-175 (schema)

  Tool metadata including description and input schema (empty Zod object, no parameters required).
  { description: 'Provides guidance on key developer decisions, including the cloud Shared Responsibility Model and a framework for "Build vs. Outsource" choices.', schema: z.object({}), },