hcp-engagement
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_API_KEY | No | API key to protect the HTTP endpoint. Always set for public deployments. | |
| SUPABASE_URL | Yes | The URL of your Supabase project. Reuse the same value as the Frescopa .env. | |
| SUPABASE_ANON_KEY | Yes | The anon (read-only) key for your Supabase project. Reuse the same value as the Frescopa .env. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hcp_list_hcpsA | List Healthcare Professionals (HCPs). Filter by specialty, tier (A|B|C), region, or state. Mock data — not real providers. |
| hcp_searchA | Search HCPs by name, NPI, or institution (partial match). |
| hcp_get_profileA | Full profile for one HCP by NPI: demographics, consent status per channel, and engagement summary. |
| hcp_list_interactionsA | List rep-HCP interactions (visits, calls, emails). Filter by HCP NPI, region, specialty, rep name, interaction type, or how many days back. |
| hcp_engagement_summaryA | Analytics: total interactions, recency, sentiment score, and samples per HCP. Sorted by most interactions first. Useful for finding engagement gaps (e.g. Tier A HCPs with no recent contact). |
| hcp_prescribing_trendsA | Monthly prescribing trend (new Rx, total Rx, market share %) for an HCP, optionally scoped to one product. Requires npi. |
| hcp_prescribing_trend_by_segmentA | Quarterly prescribing trend for one product, broken out by region and specialty (segment_rollup), plus per-HCP quarterly rows (hcp_quarterly) for drill-down into which specific HCPs are declining/growing. Use segment_rollup to compare regions/specialties side by side; use hcp_quarterly to find individual decliners within a flagged segment. |
| hcp_visit_frequency_by_segmentB | Quarterly rep interaction/visit frequency broken out by region and specialty — meant to be compared side by side with hcp_prescribing_trend_by_segment's segment_rollup for the same quarters. |
| hcp_rep_activityB | Per-rep territory summary: HCPs engaged, total interactions, interactions in last 30 days, average sentiment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zkorczyc/hcp-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server