Compatible with every major AI agent and IDE
What is the SAMHSA Treatment Locator MCP Server?
Connect to the SAMHSA Treatment Locator and empower your AI agent to find critical healthcare resources across the United States. This server provides direct access to the official Substance Abuse and Mental Health Services Administration database.
What you can do
- Geographic Search — Find facilities using precise latitude and longitude coordinates within a customizable radius.
- Service Filtering — Narrow down results using specific service codes to find the exact type of care needed (e.g., detox, inpatient, outpatient).
- Detailed Facility Profiles — Retrieve comprehensive metadata for specific facilities, including contact information and available services via unique identifiers.
- Service Code Discovery — Access the full list of available service categories and codes to refine your searches effectively.
How it works
- Subscribe to this server
- Enter your SAMHSA API Key
- Start locating treatment centers from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Healthcare Coordinators — quickly identify nearby treatment options for patients based on specific clinical needs.
- Public Health Researchers — analyze the distribution of mental health and substance use services in specific regions.
- Social Workers — find and inspect facility details directly from their workflow tools to assist clients faster.
Built-in capabilities (3)
Get detailed information for a specific facility
List available service codes used for filtering
Search for treatment facilities based on location and filters
Why Cursor?
Cursor's Agent mode turns SAMHSA Treatment Locator into an in-editor superpower. Ask Cursor to generate code using live data from SAMHSA Treatment Locator and it fetches, processes, and writes. all in a single agentic loop. 3 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
SAMHSA Treatment Locator in Cursor
SAMHSA Treatment Locator and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect SAMHSA Treatment Locator to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for SAMHSA Treatment Locator in Cursor
The SAMHSA Treatment Locator MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 3 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
SAMHSA Treatment Locator for Cursor
Every tool call from Cursor to the SAMHSA Treatment Locator MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I search for treatment facilities near a specific set of coordinates?
Use the search_facilities tool by providing the lat (latitude) and lon (longitude) parameters. You can also specify a radius in miles to define the search area.
Where can I find the list of service codes to filter my search?
You can run the list_services tool. It will return all available service categories and their corresponding codes which you can then use in the service_code parameter of search_facilities.
Can I get the full contact information for a specific facility if I have its ID?
Yes! Use the get_facility tool with the facility_id. This will retrieve detailed information including the address, phone number, and the full list of services provided by that location.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
BugHerd
10 toolsManage visual feedback and bug reports via BugHerd — track projects, tasks, and users directly from any AI agent.

AT&T IoT
10 toolsIoT Control Center -- Manage SIM devices, activation, data pools, shared plans, and connectivity diagnostics via AT&T IoT API.

Azure Synapse Analytics
7 toolsManage your Azure Synapse data pipelines seamlessly — audit Spark pools, SQL pools, datasets, and integration pipelines via your AI agent.

Kameleoon
10 toolsManage A/B testing, personalization, and experimentation workflows via AI agents.
