Use this when the user asks to see, choose, or look up their documentation Spaces, especially before using tools that need a numeric space_id. Read-only: returns accessible Spaces and does not change settings or documents.
ConnectorOAuth
604,399 tools. Updated 2026-09-23 19:38
"SpaceX" matching MCP tools:
- Use this when the user wants to read the full markdown content of a specific Space document/page after search or listing. Read-only: returns the selected document without changing content. Requires the document ID from list-space-documents, search-space-documents, or global-search.ConnectorOAuth
- Use this when the user asks how many Autopilot/repository-sync suggestions are pending, snoozed, done, high-confidence, or waiting for review. Read-only: returns grouped counts without changing suggestions or documents. Optionally filter by numeric space_id.ConnectorOAuth
- Query the verified FCC satellite licensing docket — every space-station (SAT) filing in the FCC's own daily IBFS database dump, back to the 1960s — by applicant, application type, status, and filing date. Use this for "who is authorized to operate what in orbit, what has been filed, and where does each filing stand" questions — the satellite-buildout licensing pipeline. Each filing carries the FCC's public filing key (`file_number`, e.g. "SATLOA2025061800149"), the `callsign` (e.g. "S3069" = SpaceX Gen2), the application type and status in the FCC's OWN vocabulary — verbatim codes plus the FCC's own decode text from the same dump vintage (`app_type_code` "LOA" = Launch and Operating Authority, "STA" = Special Temporary Authority, "MOD" = Modification; `status_code` "A/C" = Action Complete, "ATPN" = Action Taken Public Notice — codebooks in describe) — the full lifecycle date family (filed / granted / expires / …), the FCC's plain-English `description` of the filing, and the applicant identity (`applicant_name`, the FCC's verbatim registrant, e.g. "Space Exploration Holdings, LLC"). Filter by `applicant_name`, `app_type_code`, `status_code`, `callsign`, `file_number`, `state` (the APPLICANT's address state), `applicant_country`, `report_period` (the filing date) via `report_period_from`/`report_period_to`, or `date_grant`/`date_expire` ranges. Group by any of `applicant_name`, `app_type_code`, `status_code`, `state`, `applicant_country`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key). Example: `{"applicant_name": "Space Exploration Holdings, LLC", "group_by": ["app_type_code"]}` for one operator's filing mix; `{"report_period_from": "2020-01-01", "group_by": ["applicant_name"], "order_by": "source_record_count", "top_n": 10}` for the most active filers of the 2020s. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every record cites its exact row in the FCC's dump, re-verifiable via get_source_evidence_v1. THE ENGRAVED BOUNDARY: new-filing intake into IBFS structurally ENDED at the FCC's ICFS system cutover (~mid-2025), and ICFS publishes no bulk data — so filings SUBMITTED after the cutover are not in this docket, and counts near/after 2025 UNDERCOUNT new filing activity (say so when answering; every response carries an icfs_cutover note). Status and lifecycle updates on the filings that ARE here continue to flow daily. A filing is an authorization EVENT: never a satellite count (one NGSO grant can cover thousands of satellites), never an orbital catalog (satellites in orbit are not served here), never launch activity (FAA data, not served here). `state`/`applicant_city` are the APPLICANT's mailing address — satellites are not in states. Earth stations (SES) and non-satellite FCC dockets are out of scope. The one measure is `source_record_count` (filings in scope).ConnectorNo auth
- Use this when the user wants a Markdown export of selected Space pages, folders, or docs that can be returned in the MCP response. Read-only: returns merged Markdown without changing Space content. Use browser guidance for PDF, ZIP, or download-only export flows.ConnectorOAuth
- Resolve which Space Monkey projects this API key can read. Call this first when the user names a company rather than a project ID, and match on companyName — never silently mix projects.ConnectorOAuth
Matching MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides access to live SpaceX data including latest launches, upcoming launches, and company information through the SpaceX API.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying SpaceX launches, rockets, crew, and Starlink satellite data via MCP tools.3 npmMIT
Matching MCP Connectors
SpaceX MCP — wraps SpaceX API v4 (free, no auth)
Rocket launch schedule: SpaceX, Falcon, Electron. $0.01/query, free testnet funds.
- Resolve which Space Monkey projects this API key can read. Call this first when the user names a company rather than a project ID, and match on companyName — never silently mix projects.ConnectorNo auth
- Use this when the user wants to remove an Autopilot repository link from a Space. Destructive external-provider action: deletes the link after authorization and may remove provider webhook configuration. Requires Enterprise access, manageable Space permission, space_id, and link_id.ConnectorDestructiveOAuth
- Use this when the user wants to review pending, snoozed, done, high-confidence, or filtered Autopilot/repository-sync documentation suggestions for a Space. Read-only: returns suggestion inbox items and IDs for later apply/discard/snooze tools without changing documents.ConnectorOAuth
- PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Find REAL footage of a NAMED topic on the web — the b-roll move: the speaker mentions Elon Musk, the cut shows his rocket. Query the concrete THING ('spacex starship launch', 'tesla factory'), not a mood — search_stock covers generic visuals ('busy city'), THIS covers named people, companies, products, events. Returns candidate links best-guess first; pick real footage of the subject (short clips), then fetch_url(url, as_kind='clip'), look_at_asset for the right seconds, and a cutaway or insert at the mention. Tell the user what footage you used (title + channel).ConnectorOAuth
- Use this when the user wants to create a markdown document/page in a Space from provided content. State-changing: creates the document directly after authorization. Requires numeric space_id, title, and markdown content. Use create-space-item for folders or external links.ConnectorOAuth
- Use this when the user explicitly wants to delete one existing Space document/page. Destructive state-changing action: deletes the document directly after authorization. Requires the document ID from list-space-documents or search results; use delete-space-items for folders or bulk item deletion.ConnectorDestructiveOAuth
- Use this when the user wants to turn on or resume an existing Autopilot repository sync link for a Space. State-changing external-provider action: enables the link and registers the provider webhook after authorization. Requires Enterprise access, manageable Space permission, provider access, space_id, and link_id.ConnectorOAuth
- Use this when the user wants to pause, turn off, or disable an Autopilot repository link for a Space. State-changing external-provider action: disables the link and attempts to remove the provider webhook after authorization. Requires Enterprise access, manageable Space permission, space_id, and link_id.ConnectorOAuth
- Use this when the user wants to reject, dismiss, remove from review, or discard one Autopilot/repository-sync documentation suggestion. Destructive state-changing action: marks the pending suggestion discarded directly after authorization. Requires suggestion_id from list-space-suggestions.ConnectorDestructiveOAuth
- Use this when the user wants to apply or discard multiple Autopilot/repository-sync suggestions at once. Destructive state-changing action: bulk apply can update multiple Space documents, and bulk discard removes suggestions from active review after authorization. Requires suggestion IDs from list-space-suggestions; bulk apply requires Enterprise access.ConnectorDestructiveOAuth
- PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. SEARCH for b-roll images/clips the user does not have. Two kinds of query work: generic visuals ('a busy city', 'ocean waves') AND — with kind='photo' — REAL topical subjects ('Elon Musk', 'SpaceX Starship', a company, a product) from Wikimedia/Flickr's photo record; relay each photo's license line when it carries an obligation. For real topical VIDEO use find_footage instead. Returns a VISUALLY REVIEWABLE, provider-diverse grid (Pexels/Pixabay/Openverse when configured), not a homogeneous first-provider dump. Candidates ONLY: nothing is downloaded and nothing enters the video. kind 'video' (default) or 'photo'. orientation defaults to the project's output frame, so a 9:16 edit gets vertical footage. Then call add_stock_media with the best id.ConnectorOAuth
- Get headline campaign and audience performance for a project: per-campaign performance table, single-campaign detail, list overview, engagement and send-volume trends, subscriber-growth series, and period-over-period averages. Start here for "how are we doing". Excludes engagement distribution, tag and segment summaries, growth baseline/churn decomposition and campaign consistency — use sm_get_insights_advanced for those. Excludes campaign fatigue, subject-line keywords, send-time heatmap, monthly trend and audience health — use sm_get_insights_expert. For the member-composition view (status, rating, rep and language counts) use sm_get_member_overview, and for signup cohorts, churn and retention use sm_get_member_growth; the list overview and subscriber-growth series here are Mailchimp-list and audience-trend views, not member-level lifecycle. All three insight tiers also return campaign averages, previous-period averages, audience summary and auto-generated insights.ConnectorOAuth
- Load one sync run's full detail — per-stage results, progress, lookback window and pending batch count. Use after sm_list_sync_runs to explain why data is stale or a run failed. Failure detail lands in one of two places and rarely both: orchestration failures set run.errorMessage with no stage rows, while per-data-type failures leave it null and record the message on results[].errorMessage, so check both and treat status as the failure signal.ConnectorOAuth
- Get headline campaign and audience performance for a project: per-campaign performance table, single-campaign detail, list overview, engagement and send-volume trends, subscriber-growth series, and period-over-period averages. Start here for "how are we doing". Excludes engagement distribution, tag and segment summaries, growth baseline/churn decomposition and campaign consistency — use sm_get_insights_advanced for those. Excludes campaign fatigue, subject-line keywords, send-time heatmap, monthly trend and audience health — use sm_get_insights_expert. For the member-composition view (status, rating, rep and language counts) use sm_get_member_overview, and for signup cohorts, churn and retention use sm_get_member_growth; the list overview and subscriber-growth series here are Mailchimp-list and audience-trend views, not member-level lifecycle. All three insight tiers also return campaign averages, previous-period averages, audience summary and auto-generated insights.ConnectorNo auth
- Load one sync run's full detail — per-stage results, progress, lookback window and pending batch count. Use after sm_list_sync_runs to explain why data is stale or a run failed. Failure detail lands in one of two places and rarely both: orchestration failures set run.errorMessage with no stage rows, while per-data-type failures leave it null and record the message on results[].errorMessage, so check both and treat status as the failure signal.ConnectorNo auth