How It Works
Scout uses Context Providers to connect to your systems and retrieve information on demand:| Provider | What It Accesses |
|---|---|
| Web | Public URLs, documentation sites |
| Slack | Channel history, threads, search |
| Google Drive | Documents, spreadsheets, presentations |
| Database | CRM records, product data |
| Wiki | Internal documentation (Git-backed or Notion) |
| MCP | Any tool exposed via Model Context Protocol |
Self-Building Knowledge
As Scout answers questions, it maintains two internal systems. See Knowledge & CRM for details.| System | Purpose |
|---|---|
| Wiki | Curated facts about your company: org structure, product names, key metrics |
| CRM | People and relationships: who works on what, who to ask about X |
Run Locally
See Setup guide for detailed instructions.http://localhost:8000/docs.
Connect to the Control Plane
- Open os.agno.com
- Click Connect OS → Local
- Enter
http://localhost:8000
Deploy to Railway
See Deploy to Railway for JWT setup and production configuration.- Open os.agno.com
- Click Connect OS → Live
- Enter your Railway domain
Configure Providers
Scout’s power comes from the providers you connect. Start with one or two, then add more as needed.Slack
See Slack setup for bot creation and permissions.Google Drive
See Google Drive setup for service account configuration.MCP Servers
See MCP setup for server configuration. Connect any MCP-compatible tool:Example Prompts
Try these after connecting your providers:- What’s the status of Project Phoenix?
- Who should I talk to about billing issues?
- Summarize last week’s engineering discussions
- What decisions were made in the Q3 planning doc?