Ollagraph MCP server
An MCP server that exposes the full Ollagraph API (148 endpoints across fetch, extract, audit, intelligence, and AEO/SEO) as tools your AI agent can call directly.
Works with Claude Desktop, Cursor, Cline, Continue, and any other MCP-capable client. Built on FastMCP — the server is a thin wrapper around our published OpenAPI spec, so every endpoint stays in lockstep with the API.
Quick start
# Get an API key from https://ollagraph.com/signup (free, 1,000 credits)
export OLLAGRAPH_API_KEY="osk_..."
# Run the server
pipx run ollagraph-mcp
# or
pip install ollagraph-mcp && ollagraph-mcp
Use with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"ollagraph": {
"command": "pipx",
"args": ["run", "ollagraph-mcp"],
"env": {
"OLLAGRAPH_API_KEY": "osk_..."
}
}
}
}
Restart Claude Desktop. The tools (scrape, extract_clean, aeo_page_audit,
etc.) appear in the tool list.
Use with Cursor / Cline / Continue
Same config shape. Each client has its own MCP config location; see their docs.
Use with the MCP Inspector
npx @modelcontextprotocol/inspector pipx run ollagraph-mcp
Opens the Inspector UI for poking the tools directly.
What this gives you
- 73+ tools, one per Ollagraph endpoint, auto-generated from our OpenAPI spec
- Tool descriptions pulled from operation summaries — the LLM reads them to decide which to call
- Bearer auth handled for you; just set
OLLAGRAPH_API_KEYonce - Stays in sync with the API: when we ship a new endpoint, restart the server and your agent gets the new tool
Configuration
| Env var | Default | Description |
|---|---|---|
OLLAGRAPH_API_KEY |
(required) | Bearer token from your Ollagraph account |
OLLAGRAPH_API_URL |
https://api.ollagraph.com |
Override for self-hosted deployments |
OLLAGRAPH_TIMEOUT_SECONDS |
60 |
Per-tool-call HTTP timeout |
License
MIT.
Metadata
Release files for ollagraph-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ollagraph_mcp-0.1.0.tar.gz | 6.0 kB | Without provenance | Details for ollagraph_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ollagraph_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ollagraph_mcp-0.1.0-py3-none-any.whl |
Total release size: 13.5 kB
Release files / ollagraph_mcp-0.1.0.tar.gz
| Download URL | ollagraph_mcp-0.1.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba0a03dcddc33934871a4b4c08f4bb87671384b72d21bb65819a879d615b858d
|
|
BLAKE2b-256 checksum How to use checksums |
797d63691e9a686536f3f770ae147e09f2e72c657790b4c2e0a968cfe7d258cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Release files / ollagraph_mcp-0.1.0-py3-none-any.whl
| Download URL | ollagraph_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2bd878249688a58af9719aaba631898ed1a2c037f37264d924d9951a6dfdef2a
|
|
BLAKE2b-256 checksum How to use checksums |
15d4d37a44b22a6acfcdb34ab991d405efb08613878fdf308005a4fded9cec7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for ollagraph-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.