You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fern/products/docs/pages/ai/mcp-server.mdx
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,4 +17,17 @@ Developers can access your MCP server by visiting `your-documentation-site.com/m
17
17
18
18
<Tip>
19
19
**Looking for Fern's own MCP server?** If you want to connect your AI client to Fern's MCP server for help with Ask Fern, Docs, and SDKs, see the [fern-mcp-server repository](https://github.com/fern-api/fern-mcp-server).
20
-
</Tip>
20
+
</Tip>
21
+
22
+
## Additional AI Tooling
23
+
24
+
LLMs can access your documentation programmatically, even for authenticated sites. When content is fetched this way, it's served as clean markdown without HTML markup, making it token efficient for LLMs to process.
25
+
26
+
```bash
27
+
curl -X GET https://docs.example.com/platform/overview \
28
+
-H 'Accept: text/plain' \
29
+
-H 'x-fern-host: docs.example.com' \
30
+
-H "FERN_TOKEN:${JWT}"
31
+
```
32
+
33
+
For sites with authentication, LLMs can obtain a JWT by calling the [`/api/fern-docs/get-jwt`](/learn/docs/ai-features/mcp-server/api-reference/get-jwt) endpoint with a Fern API key. This JWT can then be used to access protected documentation content and search functionality.
0 commit comments