MCP Integration
Using SchoolScout with AI assistants via Model Context Protocol
Overview
SchoolScout provides a Model Context Protocol (MCP) server that allows AI assistants (Claude, etc.) to access education data through natural language. The MCP server is a thin proxy over the SchoolScout API.
How It Works
The MCP server exposes SchoolScout API operations as tools that AI assistants can call. Each tool maps to one or more API endpoints:
| MCP Tool | API Endpoint |
|---|---|
search_districts | GET /api/v1/districts |
get_district_details | GET /api/v1/districts/{id} |
get_buying_signals | GET /api/v1/districts/{id}/buying-signals |
search_schools | GET /api/v1/schools |
search_contacts | GET /api/v1/contacts |
generate_email | POST /api/v1/contacts/{id}/generate-email |
get_vendor_stack | GET /api/v1/districts/{id}/vendors |
manage_lists | GET/POST /api/v1/lists |
Authentication
MCP clients authenticate via OAuth and receive Bearer access tokens. For direct API access outside MCP, use API keys from Settings > API Keys.
Example Usage
With an MCP-enabled AI assistant:
"Find school districts in Colorado with more than 10,000 students that are actively looking for new LMS solutions"
The assistant will:
- Call
search_districtswith state=CO and student count filter - Call
get_buying_signalsfor matching districts - Filter for LMS-related signals
- Present a summarized report
Setup
Refer to the SchoolScout dashboard settings for MCP server configuration details, including the server URL and authentication credentials for your organization.