Metadata-Version: 2.4
Name: sitepulsar-mcp
Version: 0.1.0
Summary: Stdio launcher for the SitePulsar hosted MCP server — AEO (Agent Experience Optimization) audits measuring how findable, readable, and usable a site is to AI answer engines and autonomous AI agents.
Project-URL: Homepage, https://www.sitepulsar.ai
Project-URL: Repository, https://github.com/SitePulsar/mcp-server
Project-URL: Documentation, https://www.sitepulsar.ai/llms.txt
Project-URL: Bug Tracker, https://github.com/SitePulsar/mcp-server/issues
Author-email: Gijs van Bueren / SitePulsar <info@sitepulsar.ai>
License: MIT
Keywords: aeo,agent-infrastructure,agent-readiness,ai-agents,ai-visibility,answer-engine-optimization,anthropic,claude,mcp,model-context-protocol
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Topic :: Software Development :: Libraries
Requires-Python: >=3.10
Description-Content-Type: text/markdown

# sitepulsar-mcp

Stdio launcher for the **SitePulsar** hosted MCP server.

SitePulsar runs **AEO (Agent Experience Optimization)** audits — it measures how
**findable, readable, and usable** a website is to AI answer engines and
autonomous AI agents, returning one Agent Readiness Score across three pillars:
**FIND / READ / USE**. It is agent infrastructure, not SEO tooling.

> The SitePulsar MCP server is **remote** (streamable-http). Most MCP clients can
> connect to the URL directly and don't need this package. This package targets
> clients that require a local stdio command bridge.

---

## Install

```bash
pip install sitepulsar-mcp
```

## The remote endpoint

```
https://sitepulsar-mcp.vercel.app/mcp
```

Authenticate with **OAuth** (the connector flow, no key) or a **Bearer API key**
(Pro/Business — header `Authorization: Bearer <mcp_api_key>`).

---

## Usage

### Remote-capable clients (preferred)

Point your client straight at the endpoint — no package required:

```json
{
  "mcpServers": {
    "sitepulsar": {
      "url": "https://sitepulsar-mcp.vercel.app/mcp"
    }
  }
}
```

### Stdio-only clients

> **Status:** a native Python stdio→remote bridge is **not implemented yet**
> (see the TODO in `sitepulsar_mcp/__main__.py`). Running `sitepulsar-mcp` today
> prints connection guidance rather than serving an MCP transport.

Until the native bridge lands, use the Node `mcp-remote` proxy as the stdio
bridge:

```bash
npx mcp-remote https://sitepulsar-mcp.vercel.app/mcp
```

or the SitePulsar npm launcher (same effect):

```bash
npx @sitepulsar/mcp-server
```

Example stdio client config:

```json
{
  "mcpServers": {
    "sitepulsar": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://sitepulsar-mcp.vercel.app/mcp"]
    }
  }
}
```

---

## Links

- Website: https://www.sitepulsar.ai
- Tool/docs manifest (LLM-readable): https://www.sitepulsar.ai/llms.txt
- Contact: info@sitepulsar.ai

## License

MIT © Gijs van Bueren / SitePulsar
