Tools, resources, and prompts

Current SatellyteAI MCP Server surface for agent workflows.

The MCP server exposes tools for active work, resources for reusable context, and prompts for guided agent workflows.

Tools

Area	MCP surface	Purpose
Utilities	`ping`, `health_check`, `get_server_info`, `get_auth_context`	Server health, metadata, and auth context checks.
Discovery	`discover_companies`, `discover_people`	Company and people discovery with filters and cursor support.
Composite prospecting	`prospect_accounts`	Agent workflow plan for discover, signals, contacts, and optional enrichment. `dry_run` defaults to true.
Company identity and signals	`resolve_company_identity`, `get_company_signals`	Bidirectional domain/LinkedIn resolution and consolidated signal lookup.
Contacts	`find_contacts`, `waterfall_icp_contacts`	Contact discovery by strategy; waterfall remains separate because its cascade output differs materially.
Enrichment	`enrich_contact`	Email and/or phone enrichment through one consolidated interface.
Radar and leads	`list_radars`, `create_radar`, `get_radar_signals`, `get_radar_leads`, `push_leads`, `export_leads`	Radar management, signal review, lead review, push, and export workflows.
Outreach feedback	`record_outreach_outcome`, `get_feedback_insights`	Record outreach outcomes and review feedback analytics.

Resources

Resource	Purpose
`satellyte://meta/field-values`	Reusable Public API field values and allowed values for agent context.
`satellyte://account/info`	Account, key, workspace, and credit usage context where available.

Prompts

Prompt	Purpose
`signal_based_prospecting`	Guides an agent through signal-led prospecting.
`account_research`	Guides an agent through account research using available Satellyte context.

Credit-sensitive tools

These tools are credit-sensitive when they perform live Public API work:

Tool	Credit behaviour
`discover_companies`	Charged when the backend reveals company profiles.
`discover_people`	Charged when the backend reveals people profiles.
`get_company_signals`	Charged according to the selected signal path/action key.
`find_contacts`	Charged according to backend contact discovery behaviour.
`waterfall_icp_contacts`	Charged according to backend waterfall contact behaviour.
`enrich_contact`	Charged per enriched field when the backend charges.
`resolve_company_identity`	Charged when the backend resolver charges.
`get_radar_signals`	Charged according to backend radar signal behaviour.
`push_leads`	Charged when the backend import/push action charges.
`prospect_accounts`	Credit-safe by default with `dry_run: true`; live steps may charge when executed.

Non-credit-sensitive surface

These currently remain non-credit-sensitive unless backend behaviour changes later:

Surface	Capability
`health_check`	Health check.
`list_radars`	List existing radars.
`create_radar`	Create radar.
`get_radar_leads`	Read radar leads.
`export_leads`	Export leads.
`record_outreach_outcome`	Record feedback event.
`get_feedback_insights`	Read feedback insights.
`satellyte://account/info`	Account key info and credit usage context.
`satellyte://meta/field-values`	Meta field values.

Important implementation notes

MCP is capability-based, not a strict route mirror. A single MCP tool can intentionally cover several Public API endpoints.

lookup_company is not currently exposed as a real MCP tool. Until a backend single-entity lookup endpoint exists, lookup-style workflows should use:

resolve_company_identity
  -> get_company_signals
  -> find_contacts
  -> optionally enrich_contact

Do not present lookup_company as production-complete until the backend dependency exists.