
Sage Veterinary Imaging
from sageveterinary
Public MCP server for veterinary diagnostic imaging โ 800+ provider directory, pricing, locations, educational content, and clinical resources for dogs and cats
๐ฅ๐ฅ๐ฅโ VerifiedAccount requiredNeeds API keys
Sage MCP Public
Model Context Protocol server for Sage Veterinary Imaging's public data.
What It Serves
| Table | Records | Description |
|---|---|---|
content | 536 | Website pages, blog posts, conditions, education articles |
providers | 808 | Veterinary imaging provider directory (40 states) |
pricing | 33 | SVI imaging service pricing |
locations | 3 | SVI facility details (Round Rock TX, Spring TX, Sandy UT) |
MCP Tools
search_contentโ Full-text search across all website contentget_pageโ Get a specific page by URL slugsearch_providersโ Search 800+ vet imaging facilities by location/modalityget_providerโ Provider detail by slugget_pricingโ SVI service pricing, filterable by categoryget_location_infoโ SVI location details (address, phone, modalities)get_company_infoโ Company info, FAQs, policiesget_service_infoโ Imaging service descriptions
Architecture
GitHub โ Railway (FastAPI + MCP) โ Supabase (PostgreSQL + PostgREST)- No PHI. Completely separate from the clinical MCP server.
- Supabase REST API for all queries (no direct DB connections needed).
- Full-text search via PostgreSQL tsvector indexes.
Local Development
pip install -r requirements.txt
cp .env.example .env # Add your Supabase credentials
python -m server.mainServer runs at http://localhost:8000
- Health:
GET /health - MCP:
POST /mcp
Copy & paste โ that's it
pip install -r requirements.txt
cp .env.example .env # Add your Supabase credentials
python -m server.mainBefore it works, you'll need: SUPABASE_SERVICE_KEY
Deployment
Railway
- Connect this repo to Railway
- Set environment variables:
SUPABASE_URLโ Supabase project URLSUPABASE_SERVICE_KEYโ Service role JWTPORTโ Railway sets this automatically
Content Refresh
Run the sync worker to re-scrape website content:
python -m sync.refreshSet up as a Railway cron service for weekly refresh.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.