Fern MCP for AI. Make your documentation instantly searchable by AI.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Fern manages and expands your entire documentation ecosystem. Connect this MCP to let your agent chat with specific knowledge domains using AI completion, index new websites automatically, or pull user analytics.
It's how you make sure your docs stay searchable and up-to-date for any employee.
What AI agents can do with Fern Automation
Get jwt
Generates a secure JSON Web Token (JWT) using your API key for authorized access.
Get recent queries
Retrieves analytics data, including the most recent questions asked by users against documentation domains.
Get search key
Provides Algolia search credentials needed to connect external applications to your content index.
Your agent answers complex questions by querying specific, defined sections of your documentation.
You trigger new crawling jobs to make entire websites or directories searchable for the AI assistant.
Your agent verifies a user's current authentication status and basic profile details.
You pull reports showing what questions users have asked recently, helping you spot content gaps.
The MCP creates necessary JWTs and Algolia search credentials for secure application access.
Ask an AI about this
Waiting for input…
What AI agents can do with Fern: 6 Tools for Docs Management
These tools let your agent perform critical tasks like triggering crawls, checking user identity, or chatting with specific knowledge bases.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Fern on VinkiusGet Jwt
Generates a secure JSON Web Token (JWT) using your API key for authorized access.
Get Recent Queries
Retrieves analytics data, including the most recent questions asked by users against...
Get Search Key
Provides Algolia search credentials needed to connect external applications to your...
Index Website
Initiates a new crawling job, making the entire specified website searchable for the...
Post Chat Completion
Sends a question to the Ask Fern AI assistant and receives an answer based on your...
Whoami
Checks and reports the current user's authentication status and basic details.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Fern, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Fern. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Documentation knowledge bases are constantly out of date., Solved with Vinkius AI Gateway
Today, updating technical guides means logging into the documentation platform dashboard. You check one tab for analytics, another to see if a specific site folder was crawled, and yet another to generate new search credentials for your apps. It's manual clicking, copy-pasting API keys, and hoping nothing breaks.
With this MCP, you tell your agent what needs to happen—like 'Index the entire v2 API section.' The agent handles the complex multi-step process behind the scenes. You get an instant confirmation that the content is live, searchable, and ready for users.
Ask Fern: Instant Answers Across Domains
Before this MCP, if a user asked a question that touched on both billing policies and API usage, you had to manually route the query or write an FAQ covering both areas. This was slow and prone to conflicting information.
Now, using `post_chat_completion`, your agent can read across defined domains—say, 'billing' and 'API usage'—and synthesize one coherent answer immediately. It makes cross-domain support instant.
What your AI can actually do with this
This connector lets your agent manage the life cycle of technical documentation. Instead of manually running separate jobs to check if content is indexed or if a feature is working, you simply tell your AI client what you need done. You can trigger new crawling jobs to include updated guides or instantly get answers from specific sections using advanced chat completion.
Plus, it gives you insight into how users actually interact with the material by retrieving recent queries and providing secure access tokens for external applications. Because Vinkius hosts this MCP, your agent connects once and gains control over the entire documentation process, letting you manage everything from analytics to content publishing.
019ea5eb-4489-7138-a7b9-72086927642b Here's how it actually works
The bottom line is you control complex, multi-step documentation operations using simple commands from your favorite AI client.
Subscribe to this MCP on Vinkius, providing your unique Fern API Key and required tokens.
Your agent authenticates with the connection details and confirms it can run documentation management tasks.
You invoke a tool through your preferred AI client to perform actions like indexing or chatting.
Who is this actually for?
Technical Writers and Content Engineers. You're the person whose job it was supposed to be: making sure the docs are accurate and easy to find. The pain is knowing that even if you write a perfect guide, nobody can find it because the search index is outdated or broken.
You use this MCP to trigger website indexing after publishing new guides and check user credentials before content goes live.
You ask your agent to interact with the Ask Fern AI assistant, getting instant answers about complex product features for end-users.
You pull recent queries and analytics using this MCP. This data shows exactly where users are struggling or what documentation you need to write next.
What Changes When You Connect
You stop guessing if content is indexed. Use the index_website tool to force a full crawl, guaranteeing new guides are immediately available for search and AI querying.
Instead of manually checking logs or dashboards for user questions, you run get_recent_queries. This gives instant visibility into pain points—the exact topics your users need help with right now.
The post_chat_completion tool allows agents to answer complex support questions by reading across multiple documentation domains in one go. It makes 'Ask Fern' a true knowledge expert.
You gain control over security and access using get_jwt and get_search_key. This lets you programmatically manage who sees what, which is critical for enterprise applications.
The whoami tool verifies user permissions on demand. You can build workflows that check authentication before letting the agent touch sensitive documentation sections.
See it in action
New guides were just published and nobody can find them.
A Technical Writer needs to make sure a whole new section of API docs is searchable immediately. Instead of waiting for a nightly crawl, they use their agent to run index_website on the new subdirectory, ensuring instant visibility.
Support tickets are piling up because users can't figure out basic setup.
A Product Manager wants to find the top three confusing topics. They use their agent to call get_recent_queries, immediately getting a list of common failures, allowing them to write preventative content.
An external partner application needs read-only access to API docs.
A Developer uses the MCP to execute get_jwt and get_search_key. This securely provides credentials that only work for the specific documentation scope, keeping user data protected.
The team needs an instant answer about a niche configuration setting.
A Support Engineer asks their agent to run post_chat_completion with a complex question. The tool queries the correct domain and returns an accurate, sourced answer immediately.
The honest tradeoffs
Assuming content is automatically indexed.
The user writes 50 pages of new documentation but then forgets to manually trigger a crawl job before announcing the update. The AI assistant responds with, 'I don't know,' leading to frustrated support calls.
Don't rely on passive updates. After publishing content, always run index_website via your agent. This ensures the new material is live and searchable for all tools.
Using general search when specific knowledge is needed.
The user asks their agent a question using a generic API endpoint that searches everything, leading to vague results mixed with unrelated product data. The answer is unusable.
Always use the post_chat_completion tool and specify the correct documentation domain in your prompt. This narrows the search context down to the source of truth.
When It Fits, When It Doesn't
Use this MCP if your biggest pain point is keeping technical knowledge bases accurate, findable, and actionable for both humans and AI agents. You need programmatic ways to manage content lifecycles, check security permissions (get_jwt), or understand user behavior (via get_recent_queries). Don't use this if you just need a simple text editor or a general API wrapper; those tools won't help you index an entire site or chat with specialized documentation. If your goal is simply to write code, you don't need this—you need a generic coding utility instead.
Questions you might have
How do I use the Fern MCP to make sure my new website content is searchable? +
You run the index_website tool through your agent, specifying the full URL you want indexed. The system handles triggering the crawl and updating the search index for AI access.
What data does get_recent_queries provide about my users? +
This tool pulls raw analytics showing a list of recent questions asked by your user base, allowing you to identify gaps in your documentation or confusing topics immediately.
Can I use the Fern MCP for secure application integration? +
Yes. You can execute get_jwt and get_search_key. These tools generate the necessary access tokens and Algolia keys needed to connect external applications securely.
How does post_chat_completion work with different knowledge sections? +
You simply instruct your agent via the tool prompt, specifying which documentation domains it should use. The assistant then synthesizes a single answer from all provided contexts.
Is whoami useful for verifying my API client's status? +
Yes. Running whoami checks your current authentication status and user details, which is useful for building internal workflows that require identity validation before running other tools.
We've already built the connector for Fern. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.