Skip to main content
Glama

AstroFabric MCP Server

AstroFabric is agentic AI for business intelligence: autonomous data infrastructure that turns strategic objectives into verified datasets and live intelligence streams. Its agents discover companies and people, execute deep enrichment, verify corporate and contact records, monitor real-time business and marketplace signals, score and segment targets, build matched audiences, and deliver structured intelligence into CRMs, commerce systems, ad platforms, operational sheets, messaging channels, or any application through REST, MCP and CLI. Every workflow carries evidence and operates within approval gates, audit trails and credit ceilings. This MCP server puts that infrastructure behind your editor, give mission_agent an open-ended objective in plain language and it plans and executes the mission, returning the finished data with the evidence behind it..

This repository is both the connector for the hosted AstroFabric MCP endpoint (add the remote URL with your API key and start working) and a runnable stdio server for clients that prefer a local process - see Run it locally.

Prerequisites

  1. An AstroFabric workspace on a paid plan - sign up at https://www.astrofabric.ai

  2. An API key: in the AstroFabric console, open API keys → Create key, and copy the ek_live_... token (it is shown once).

Related MCP server: Agentic Control Framework (ACF)

Setup

Every client uses the same endpoint (https://www.astrofabric.ai/api/mcp) and the same key. Pick yours:

claude mcp add --transport http astrofabric https://www.astrofabric.ai/api/mcp --header "Authorization: Bearer ek_live_YOUR_KEY_HERE"

Add a custom connector with the bare URL and sign in when prompted - the server walks you through AstroFabric sign-in and hands the client a scoped key you can revoke from the console:

https://www.astrofabric.ai/api/mcp

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "astrofabric": {
      "url": "https://www.astrofabric.ai/api/mcp",
      "headers": { "Authorization": "Bearer ek_live_YOUR_KEY_HERE" }
    }
  }
}

Add to cline_mcp_settings.json (Cline → MCP Servers → Configure, or Remote Servers → add by URL):

{
  "mcpServers": {
    "astrofabric": {
      "type": "streamableHttp",
      "url": "https://www.astrofabric.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer ek_live_YOUR_KEY_HERE"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Add to .vscode/mcp.json:

{
  "servers": {
    "astrofabric": {
      "type": "http",
      "url": "https://www.astrofabric.ai/api/mcp",
      "headers": { "Authorization": "Bearer ek_live_YOUR_KEY_HERE" }
    }
  }
}

Add to ~/.codex/config.toml:

[mcp_servers.astrofabric]
url = "https://www.astrofabric.ai/api/mcp"
http_headers = { "Authorization" = "Bearer ek_live_YOUR_KEY_HERE" }

Install the extension (OAuth - the first call opens AstroFabric sign-in in your browser):

gemini extensions install https://github.com/sam1siam/astrofabric-mcp

Or, with an API key, add to ~/.gemini/settings.json under mcpServers:

{
  "astrofabric": {
    "httpUrl": "https://www.astrofabric.ai/api/mcp",
    "headers": { "Authorization": "Bearer ek_live_YOUR_KEY_HERE" }
  }
}

Chat assistants stop a tool call after about a minute, so they use the chat surface, where a mission starts in the background and its result is collected when it is ready. Add it as a custom connector (ChatGPT developer mode) or a connected app (Gemini) and sign in when prompted:

https://www.astrofabric.ai/api/mcp/chat

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "astrofabric": {
      "serverUrl": "https://www.astrofabric.ai/api/mcp",
      "headers": { "Authorization": "Bearer ek_live_YOUR_KEY_HERE" }
    }
  }
}

Shortcut: with the CLI installed, astrofabric connect <client> prints your client's config with your key already filled in.

If your client cannot send headers, the key can ride the URL instead: https://www.astrofabric.ai/api/mcp?key=ek_live_YOUR_KEY_HERE - treat that whole URL as a secret.

Three tool surfaces

  • Default (the URL above): one tool, mission_agent - the autonomous mission runner. Best for editors: one entry in your tool list, the whole platform behind it.

  • Full catalog: append ?tools=all to the URL to also expose every individual data and execution tool (company and person data, enrichment, email verification, technographics, business signals, lists, audiences and delivery), plus any MCP servers your workspace has connected.

  • Chat (https://www.astrofabric.ai/api/mcp/chat): start_mission and get_mission_result, for chat assistants whose tool calls stop at about a minute. The mission runs in the background and each call returns within about 30 seconds.

Using it

Ask for outcomes, not steps:

"Build a list of 40 companies showing buying intent on warehouse robotics, verify emails, and draft a first touch for each."

"Enrich this account list with company size, technology stack and recent hiring signals, then return the best-fit accounts with supporting evidence."

Results start with a [thread:<id>] line. Pass that id as thread_id on follow-ups ("verify those emails", "format them for LinkedIn Ads") and the agent continues with full memory of everything already asked and delivered. It may reply with a clarifying question; answer it the same way.

Run it locally (stdio)

This repository is also a runnable stdio MCP server - the same mission_agent tool, executing missions through the AstroFabric platform with your key. For clients that prefer a local process over a remote URL:

{
  "mcpServers": {
    "astrofabric": {
      "command": "npx",
      "args": ["-y", "github:sam1siam/astrofabric-mcp"],
      "env": { "ASTROFABRIC_API_KEY": "ek_live_YOUR_KEY_HERE" }
    }
  }
}

Or with Docker: docker build -t astrofabric-mcp . && docker run -i --rm -e ASTROFABRIC_API_KEY=ek_live_... astrofabric-mcp

Prefer a terminal? The CLI

The same platform ships as a zero-dependency CLI (astrofabric on npm):

npm install -g astrofabric

astrofabric login --key ek_live_...
astrofabric run "Find 20 companies hiring SDRs, enrich their profiles and return a verified prospect list"

In a coding agent (Claude Code, Codex, Gemini CLI), the whole setup is one prompt: "Install the AstroFabric CLI for me, then run astrofabric docs to learn it." And astrofabric connect cursor (or claude-code, codex, gemini, vscode, windsurf) prints ready-to-paste MCP config per client.

Notes

  • Missions bill against your workspace's credits; the console's Usage page shows every run.

  • Writes to connected systems honor your workspace's approval settings - autonomous writes can be gated to a human approval queue.

  • OAuth 2.1 (dynamic client registration + PKCE) is also supported via standard discovery, for clients that prefer sign-in over keys.

License

The contents of this connector repository are MIT licensed. The AstroFabric platform is a commercial service.

Available Tools

1 tool
mission_agentMission Agent (autonomous missions)A

Give AstroFabric an open-ended objective across growth, revenue or digital operations in plain language and it plans and executes the whole mission autonomously: research markets, audit sites, analyze competitors, build prospect lists from buyer intent and signals, verify emails, draft outbound, produce creative, run data work in the code sandbox, deliver into connected apps, and more. The result starts with a [thread:] line - pass that id as thread_id on follow-ups ("verify those emails", "format them for LinkedIn Ads") and the agent remembers everything already asked and delivered. It may reply with a clarifying question; answer it the same way. Prefer this over the individual tools for anything multi-step.

Inputs: objective (required), thread_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    The server exposes exactly one tool, so there is no possibility of confusing it with another. All tool selection is unambiguous by definition.

    Naming Consistency4/5

    The lone tool name 'mission_agent' is clear and internally consistent, but the pattern cannot be validated across a set. No naming conflicts or inconsistencies exist.

    Tool Count3/5

    A single tool is borderline for a server that describes a broad range of capabilities. The one mission_agent can be a legitimate monolithic entry point, but the count feels thin given the scope.

    Completeness3/5

    The mission_agent handles open-ended missions and follow-ups via thread_id, but there are no explicit controls for listing, canceling, or monitoring missions. The description hints at individual granular tools that are absent from this server surface.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enterprise-grade MCP server with multi-agent system for business AI transformation across finance, healthcare, retail, and other domains. Provides specialized AI agents for data analysis, API execution, business validation, and report generation with real-time monitoring and observability.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with operational customer context, including typed revenue objects, persistent state, scoped tools, and human-in-the-loop handoffs through MCP, REST, and CLI.
      13
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP-native agentic platform orchestrating planner/executor/critic agents over hybrid RAG with three-tier memory, budget enforcement, safety guardrails, and full observability. It exposes all capabilities as MCP tools, enabling natural-language control of document ingestion, retrieval-augmented generation, and multi-step AI workflows.
      MIT