SAMHSA Treatment Locator MCP for AI. Find verified mental health services near any address.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
SAMHSA Treatment Locator connects to official Substance Abuse and Mental Health Services Administration data. It lets you find specific treatment facilities across the US using precise coordinates and filtering by service type (like detox or inpatient care).
If you need accurate, verifiable healthcare resource locations for public health analysis or client coordination, this is it.
What your AI can do
Get facility
Retrieves the full set of details for a facility when you provide its unique ID.
List services
Returns an exhaustive list of service codes, so you know exactly what types of care to filter by.
Search facilities
Searches for facilities using coordinates and filters to narrow down results based on location and service type.
Find facilities within a specific radius using latitude and longitude.
Limit search results to only include care types like detox, mental health, or outpatient services.
Retrieve all available metadata—contact details and service lists—for a known facility ID.
List every service code category used by SAMHSA, helping you build accurate search filters.
Ask an AI about this
Waiting for input…
SAMHSA Treatment Locator MCP Server: 3 Tools for Facility Data
These three tools let your agent search, list available services, and pull deep records on SAMHSA-verified treatment centers across the US.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using SAMHSA Treatment Locator on VinkiusGet Facility
Retrieves the full set of details for a facility when you provide its unique ID.
List Services
Returns an exhaustive list of service codes, so you know exactly what types of care...
Search Facilities
Searches for facilities using coordinates and filters to narrow down results based...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with SAMHSA Treatment Locator, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by SAMHSA. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Finding specialized care locations shouldn't require navigating five different government websites.
Today, finding a specific treatment center means opening multiple tabs: one for coordinates, another for service codes, and then manually cross-referencing the results against facility directories. It’s copy/pasting IDs and checking status reports across three different portals just to confirm if 'inpatient detox' is available nearby.
With this MCP server, your agent handles the whole workflow in one go. You give it a location and two criteria (e.g., 25 miles radius + DETOX code). It runs `search_facilities` and gives you a clean list of verified options. No switching tabs required.
The SAMHSA Treatment Locator MCP Server provides reliable facility data.
Manual checks waste time validating IDs, cross-referencing service lists, and ensuring the coordinates are accurate. This process is slow and prone to human error when dealing with critical patient care timelines.
The server automates this entire validation chain. It uses `list_services` for code integrity and `search_facilities` for location accuracy. You get clean data immediately—what you need, exactly when you need it.
What your AI can actually do with this
You're connecting to the SAMHSA Treatment Locator server, which gives your agent direct access to official Substance Abuse and Mental Health Services Administration data. This tool lets you find precise healthcare resources across the whole country.
To start, you use search_facilities when you need to locate a facility within a specific area. You pass latitude and longitude coordinates along with a defined radius to narrow down the search pool. When you run this search, you can restrict results based on service type—you're only looking for detox centers, or maybe inpatient care, or specialized mental health services.
This combination of location data and filtering ensures you find exactly what your client needs.
Before you even start searching, you should check the available codes. You use list_services to get an exhaustive list of service code categories used by SAMHSA. It shows you every type of care—from outpatient services to specialized treatment programs—so you never have to guess what filter code will work.
Once you've run a search and gotten a facility ID, the get_facility tool lets you pull the full report. You give it that unique ID, and it returns every bit of metadata available for that location. This includes all contact details and an exhaustive list of services the center offers.
It’s deep data—way more than just a name and address.
Here's how the process works: You first use list_services to build your knowledge base, identifying the correct codes. Next, you run search_facilities, providing coordinates and filtering by one of those verified service types. That search returns potential facility IDs. Finally, for any ID that looks promising, you use get_facility. This last step pulls all the necessary details—the comprehensive report—confirming everything from phone numbers to specific care capabilities.
You'll never have to worry about finding a resource because this system lets you verify every piece of data against official SAMHSA records.
019e38e7-8412-736c-a5b6-323ef7bd1656 Here's how it actually works
The bottom line is: You feed the server location data and known criteria; it returns verified facility information from SAMHSA.
Subscribe to the server and enter your required SAMHSA API Key.
Your agent calls list_services first. This retrieves the current list of usable service codes (like DETOX or OP).
The agent then uses search_facilities, passing in coordinates, a radius, and the specific service code(s) gathered previously.
Who is this actually for?
Anyone dealing with complex, geo-specific public health or clinical resource needs. This tool saves social workers and healthcare coordinators hours of manual database cross-referencing. It's for the researcher who needs hard data on service distribution, not just general info.
Needs to quickly find nearby treatment options for a patient based on their specific clinical diagnosis and location.
Uses the facility details tool to pull up contact info and available services directly during client intake calls, saving time.
Runs large-scale searches across specific geographic regions to analyze where mental health or substance abuse services are lacking.
What Changes When You Connect
Precision over guesswork. Instead of getting vague results, you use search_facilities to narrow down options by exact coordinates and specific service codes.
Saves research time. You don't have to guess the right filter; running list_services gives you the full list of approved SAMHSA categories upfront.
Deep data access. If a client is accepted, you use get_facility with their ID to pull comprehensive metadata—contact details and specialties—all in one call.
Scales research efforts. Public health teams can run massive searches across regions using defined radii without manually logging into separate databases.
Reduces errors. The server connects directly to the official SAMHSA database, ensuring your client always works with current, verified resource listings.
See it in action
A patient needs immediate local care options.
The coordinator enters a client's lat/long. They run search_facilities for 'detox'. The agent gets a list of nearby centers, and the coordinator immediately uses get_facility on the top result to confirm hours and contact info.
A researcher needs to map service gaps.
The researcher first runs list_services to see all available codes. Then they loop through multiple coordinates, calling search_facilities for 'Mental Health' (OP) in each area to build a heat map of coverage.
A social worker needs specific program details.
The worker has a facility ID. They skip the search and run get_facility. This instantly pulls up if that center offers specialized youth programs, allowing them to match the client's need without clicking through multiple web pages.
Filtering for complex care needs.
The user knows a facility exists but isn't sure of its codes. They run list_services first. Then they use the returned code (e.g., VET) to refine their initial search with search_facilities, hitting the target faster.
The honest tradeoffs
Searching without knowing service codes
Just telling your agent: 'Find me a mental health place in LA.' The tool might return too many general results, forcing you to manually filter through non-relevant data.
First, use list_services to confirm the right code (e.g., OP for Outpatient). Then, run search_facilities, passing both your location and that specific service code.
Over-relying on general search tools
Using a generic mapping tool to find facilities. These often lack the detailed metadata (like unique IDs or specific SAMHSA classifications) you need for compliance records.
Always use search_facilities and then follow up with get_facility. This guarantees you get the official, comprehensive record attached to the facility's ID.
Assuming all data is available at once
Asking for location details and service codes in one prompt. The API might fail or only return partial results because it needs structured inputs.
Break it down: Start with list_services to get the criteria, then use those criteria and coordinates in a separate call to search_facilities.
When It Fits, When It Doesn't
Use this server if your process requires verified healthcare resource data tied to US locations. Specifically, if you need to filter by precise service codes (detox, IP) or run searches based on latitude/longitude pairs, use the search_facilities tool. If you already have a facility ID and just need its full profile, skip search and jump straight to get_facility. Don't use this server if your goal is general travel planning or global coverage; it only handles SAMHSA data within the US. If you simply want to check what types of services are available across the board before searching, run list_services first.
Questions you might have
How do I find facilities near a specific intersection using the SAMHSA Treatment Locator MCP Server? +
You must use latitude and longitude coordinates, not street addresses. You pass these precise GPS points to search_facilities along with your desired service code.
What should I run first when using the SAMHSA Treatment Locator MCP Server? +
list_services. This tool provides a master list of all available codes (like OP or IP). Running this first ensures you use the correct filtering criteria for your search.
Can I get details on a facility without searching by location? +
Yes. If you already have the unique identifier, run get_facility and provide only that ID. It skips geo-search entirely and pulls the full record directly.
Does SAMHSA Treatment Locator MCP Server support state-by-state filtering? +
Yes, by combining geographic search with specific service codes. You use search_facilities and define both a coordinate boundary and the required service code(s) for accurate results.
How do I authenticate when using the SAMHSA Treatment Locator MCP Server? +
You must provide a valid API Key during setup. Vinkius requires this key to authorize access to the official SAMHSA database. Your AI client needs to pass this credential whenever it invokes any tool, like search_facilities.
Are there rate limits I should be aware of when running 'search_facilities'? +
Yes, the underlying SAMHSA API enforces rate limits on requests. To avoid hitting those limits, we recommend batching multiple searches together or implementing an exponential backoff mechanism in your client code.
What happens if I try to search for a service code that doesn't exist using 'search_facilities'? +
The server validates all input parameters against the official SAMHSA catalog. If you pass an invalid or deprecated service code, the API returns a clear error message detailing exactly which parameter needs correction.
Does the SAMHSA Treatment Locator MCP Server support searching outside the United States? +
No, this server uses official data from SAMHSA. Its scope is strictly limited to reporting and locating substance use and mental health facilities within the continental U.S.
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.
We've already built the connector for SAMHSA Treatment Locator. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 3 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.