# sam1siam/astrofabric-mcp [Health: Active]

**Category:** 📊 Data Platforms  
**Repository:** https://github.com/sam1siam/astrofabric-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sam1siam-astrofabric-mcp

## Description
Business intelligence: company and contact discovery, verification, enrichment, business signals, lists and governed delivery.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

**Requires environment variables:** `ASTROFABRIC_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What sam1siam/astrofabric-mcp MCP server does

The sam1siam/astrofabric-mcp MCP server exposes AstroFabric, a hosted business-intelligence platform, to MCP-compatible clients. It is designed around outcome-based requests rather than a fixed sequence of API calls. An agent can ask for a target dataset, enrichment workflow, verification task, or delivery operation, and AstroFabric plans and executes the mission.

The platform covers company and people discovery, corporate and contact record verification, enrichment, technographics, email verification, business and marketplace signals, scoring, segmentation, matched audiences, lists, and delivery. Results include evidence associated with the work. Connected destinations can include CRMs, commerce systems, advertising platforms, operational sheets, messaging channels, or other applications supported by the workspace.

## How it works

The hosted MCP endpoint is `https://www.astrofabric.ai/api/mcp` and uses Streamable HTTP. By default, it exposes one tool named `mission_agent`. This gives an editor a single entry point for the broader platform. Adding `?tools=all` exposes the individual data and execution tools as well as MCP servers connected to the workspace.

Mission results begin with a thread identifier. Supplying that `thread_id` in a later request lets the agent continue the same work with its prior context. The agent can ask clarifying questions when an objective needs more detail.

A separate chat endpoint, `https://www.astrofabric.ai/api/mcp/chat`, provides `start_mission` and `get_mission_result`. It is intended for chat surfaces that impose short tool-call limits: the mission runs in the background and the calls return within about 30 seconds.

## Setup and configuration

Using the sam1siam/astrofabric-mcp MCP server requires an AstroFabric workspace on a paid plan and an API key created in the AstroFabric console. Remote clients send the key as a Bearer authorization header. OAuth 2.1 with dynamic registration and PKCE is also available for clients that support sign-in.

The repository can run as a local stdio server with `npx -y github:sam1siam/astrofabric-mcp`, using `ASTROFABRIC_API_KEY` for authentication. It can also be built and run with Docker. If a client cannot send headers, the key may be included in the endpoint query string; that URL should be treated as a secret.

## Tools and capabilities

- Run open-ended business-intelligence missions with `mission_agent`.
- Expose the full catalog of data and execution tools with `tools=all`.
- Discover companies and people, then enrich and verify their records.
- Inspect technographics, business signals, lists, scores, segments, and matched audiences.
- Deliver structured intelligence to supported connected systems, subject to workspace controls.
- Continue a mission through `thread_id` or retrieve background results through the chat surface.

## Limitations and notes

The sam1siam/astrofabric-mcp MCP server depends on the commercial AstroFabric platform; the connector repository itself is MIT licensed, but workspace access requires a paid plan. Missions consume workspace credits, with usage shown in the AstroFabric console. Writes to connected systems follow the workspace’s approval settings and may wait in a human approval queue.

The local stdio process still executes missions through AstroFabric and therefore needs a valid API key and network access to the platform. The chat endpoint is a specialized alternative for clients whose tool calls end after roughly one minute, not a separate data platform.

_Full upstream README: https://allmcps.com/mcp/sam1siam-astrofabric-mcp/readme_