Put your docs inside the IDE via MCP
Cursor, Claude, and other MCP clients answer from your docs.
Developers now ask their AI coding assistant instead of reading your docs — and the assistant answers from stale training data, hallucinating deprecated endpoints and wrong parameter names. You get support tickets for APIs you fixed a year ago.
BeforeQuery exposes each project as an MCP server with search_docs, ask_question, and list_sources tools. Developers add one endpoint to Cursor, Claude, or any MCP client, and their AI assistant retrieves your current documentation instead of guessing — grounded answers, right in the editor.
How it works
- 1Each BeforeQuery project exposes an MCP server endpoint out of the box.
- 2Developers add the endpoint to Cursor, Claude, or any MCP client, authenticated with a client key.
- 3The AI assistant calls search_docs, ask_question, and list_sources against your current index.
- 4Answers in the editor are grounded in your live docs instead of stale training data.
What you get
Features that make it work
Frequently asked questions
What exactly does the MCP server expose?
A JSON-RPC MCP endpoint per project with three tools: search_docs (hybrid search over your index), ask_question (full RAG answer with citations), and list_sources. Any MCP-aware client can use them.
How do developers authenticate?
With a client key issued per project. Keys can be scoped, so the MCP surface only reaches the knowledge you intend to expose.
Which tools can connect to it?
Any MCP client — Cursor, Claude, and other MCP-aware editors and assistants, plus your own tooling via the @beforequery/agents SDK's MCP client.
How long does setup take?
Most teams are live the same day. You connect a source — a docs URL, GitHub repo, Notion workspace, or a file upload — and BeforeQuery crawls, normalizes, chunks, and embeds the content automatically. The website widget is a single script tag, and the Slack/Discord bots install in a few clicks. There is no model to fine-tune and no infrastructure to run.
Are answers backed by citations?
Yes. Every answer includes a structured citations list with the URL, title, and excerpt of each source used, and the answer text cites sources inline. Users can click through to verify any claim against the original document — which is what makes the answers trustworthy enough for support, sales, and internal use.
Is my content used to train AI models?
No. Your indexed content, embeddings, and conversations are isolated to your workspace and are only used to answer your own questions. Content is never shared across customers, and data is encrypted at rest and in transit. Enterprise plans add OIDC/SAML SSO, audit logs, and data-residency options.
Which knowledge sources can I connect?
18+ source types: websites, GitHub, GitLab, Notion, Confluence, Google Drive, SharePoint, Shopify, Zendesk, Jira, Linear, Salesforce, Slack, Discourse, Stack Overflow, YouTube, OpenAPI specs, and direct file uploads (PDF, Markdown, TXT, HTML). Sources sync on a schedule, and GitHub/GitLab can re-index automatically via webhooks on every push.
What happens when the AI is not confident in an answer?
Answers are confidence-scored. When retrieval confidence falls below your threshold, BeforeQuery returns a transparent, configurable fallback — typically pointing users to your support channel — instead of guessing. Those unanswered questions are logged in knowledge gap analytics so you can close the gap in your docs.
Related use cases
Unblock developers integrating your API
Answer auth, webhook, and SDK questions with code-aware AI.
Fix developer portal search
Hybrid semantic + keyword search that actually finds the page.
Q&A over your OpenAPI reference
Ask 'which endpoint updates a subscription?' and get the answer.
Ready to put your docs inside the IDE via MCP?
Connect your knowledge sources and see cited AI answers in minutes — free, no credit card required.
Get Started Free