Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.early-bird.space/llms.txt

Use this file to discover all available pages before exploring further.

​
MCP Server

Early Bird’s recommended MCP design is intentionally narrow. The goal is not to expose a raw database. The goal is to give agents a few safe, useful tools that map onto common analysis workflows.
  • earlybird.catalog
  • earlybird.dashboard_summary
  • earlybird.search_projects
  • earlybird.search_programs
  • earlybird.search_organizations
  • earlybird.get_context
  • earlybird.get_application_windows

​
Why this shape

  • Agents should not guess the schema from scratch.
  • Agents should not trigger broad fan-out request patterns by default.
  • Agents should have clear, composable tools for common analysis tasks.

​
Tool behavior expectations

Each tool should ideally return:
  • items
  • truncated
  • page
  • pageSize
  • queryCost
  • cacheHit
  • schemaVersion

​
Anti-patterns

Avoid these MCP patterns:
  • raw SQL access
  • full-table fetch tools
  • single tool that acts like an unconstrained search engine across everything
  • tools that hide pagination and silently keep crawling

​
Philosophy

The MCP layer should be a thin wrapper over the API layer, not a second product with its own independent semantics.