Docs MCP Server
This documentation site is also available as an MCP (Model Context Protocol) server, so you can connect AI assistants — Claude, Cursor, and other MCP-compatible tools — to these docs. Your assistant can then search the documentation, read full pages, and fetch OpenAPI specs while helping you build your integration.
This is a documentation server, not the API
The MCP server does not connect to the PhishFort Client API. It cannot report incidents, read your incident data, or perform any account actions. All incident operations go through the REST API with your API key.
API MCP server coming soon
A separate MCP server for the PhishFort Client API itself — with authenticated access to report and manage your incidents from an AI assistant — is coming soon. This page will link to it once available.
Endpoint
The server uses the standard streamable HTTP transport and requires no authentication — it only serves this public documentation. Your API key is not needed (and not accepted) here.
Connecting
- Go to Settings → Connectors → Add custom connector
- Name it e.g.
PhishFort API Docsand enter the URLhttps://capi-docs.phishfort.com/mcp - Leave authentication empty and save
Available Tools
All tools are read-only and return documentation content only.
| Tool | Description |
|---|---|
search_docs |
Full-text search across all documentation pages. Returns matching sections with links and snippets. |
get_doc |
Fetch a full documentation page as markdown (e.g. auth, report-incident, webhooks). |
list_docs |
List every documentation page with its slug, title, and URL. |
get_openapi_spec |
Fetch an OpenAPI (Swagger) YAML spec: incidents, single-incident, or reference. |
Example prompts
Once connected, ask your assistant things like:
- "How do I authenticate against the PhishFort Client API?"
- "Write a Python script that reports a phishing URL with two attachments."
- "What webhook events exist and how do I verify the signature?"
- "Fetch the OpenAPI spec for the incidents endpoint and generate a typed client."