Archbee MCP for AI. Manage your documentation and knowledge base from any AI client.
Works with every AI agent you already use
…and any MCP-compatible client








How this MCP server connects to your AI agent
Archbee MCP: Manage your entire technical knowledge base directly through natural language instructions. This connector lets you create, update, and manage documentation spaces, synchronize OpenAPI specs, and query deep product guides without leaving your AI client.
It’s the direct pipeline to keeping your company's technical documentation current and searchable.
What AI agents can do with Archbee Automation
Clone space
Makes a complete duplicate copy of an existing documentation space structure.
Create space group
Gathers multiple spaces into one logical container group for better organization.
Create space
Builds a brand-new, empty documentation space from scratch.
You can build new documentation areas using create_space, update existing ones with update_space, clone structures via clone_space, or organize related spaces into groups using create_space_group.
The MCP lets you write new documents or revise old ones using create_update_doc; it can also pull existing content with get_doc and delete documents when they are retired.
You can quickly add formatted Markdown content using import_content, or automatically sync structured API data by running sync_openapi against an OpenAPI definition.
The agent searches across your entire organization's knowledge base with search_docs and retrieves specific details about API definitions using info_openapi.
You can export the whole organization data via export_organization, or even retrieve configuration settings by calling get_display_rules.
Ask an AI about this
Waiting for input…
What AI agents can do with Archbee: 20 Tools for Knowledge Management
These tools give you granular control over every aspect of your documentation lifecycle, from creating new content to synchronizing complex API definitions.
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 Archbee on VinkiusClone Space
Makes a complete duplicate copy of an existing documentation space structure.
Create Space Group
Gathers multiple spaces into one logical container group for better organization.
Create Space
Builds a brand-new, empty documentation space from scratch.
Create Update Doc
Adds new content to a document or modifies the text of an existing one.
Delete Doc
Permanently removes a specific documentation file from the system.
Delete Space Group
Removes an entire grouping of related spaces.
Delete Space
Permanently wipes out an entire documentation space and all its contents.
Discard Suggestion
Tells the agent to ignore a suggested change it has made to a document.
Get Display Rules
Retrieves all organizational settings that dictate how documentation appears to...
Export Organization
Downloads a complete copy of the entire organization's data for backup or migration...
Get Doc
Retrieves and shows the full text content of a specific document by its ID.
Import Content
Takes raw Markdown text and inserts it into an existing or new document.
Info Openapi
Provides metadata and structure details about a previously synchronized OpenAPI definition.
Merge Suggestion
Combines changes from a suggested draft document into the primary, published version...
Publish Space
Makes a documentation space live and available to users in a specific environment.
Search Docs
Searches through the text content of all documents within your organization's...
Sync Openapi
Connects a structured OpenAPI definition file to a specific document tree, enabling...
Update Space
Changes the general metadata or settings of an entire documentation space.
Upload File
Adds a file, like a diagram or image, into the Archbee storage area.
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 Archbee, 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
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 19 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The headache of keeping product guides current., Solved with Vinkius AI Gateway
Every time a backend API changes, or Product Management updates a core requirement, someone has to remember to open the right guide, find the correct section, and manually rewrite the documentation. This means copy-pasting endpoints from Jira tickets into Markdown files, then having to publish those guides across multiple staging environments just to test it.
With this MCP, you tell your agent what changed. It handles the sequence: finding the affected space, calling sync_openapi with the new definition, and finally publishing the updated documentation—all without a single human click.
Archbee MCP gives you total control over content lifecycles.
You eliminate manually creating spaces or groups just to keep related guides together. You can tell your agent, 'Group all onboarding materials,' and it uses create_space_group to handle the entire organizational structure change instantly.
It’s not just about writing; it's about architecture. Your AI client now manages the document flow—from initial import via import_content to final publication using publish_space. It keeps your knowledge base running like a machine, not a pile of files.
What your AI can actually do with this
Connecting Archbee gives your agent full control over your technical writing workflows. You can treat your entire knowledge base like a single document—you don't have to jump between tools or interfaces to find information. For instance, you can ask it to perform a global search across every guide and requirement the company has ever written.
Need to update an API definition? The MCP lets you sync OpenAPI specs right into specific documentation trees, making sure your 'Try It' features are always up to date. If your current workflow is scattered across multiple systems, connecting Archbee via Vinkius gives you one central place where your AI client handles all the complexity, letting you focus only on what needs writing or fixing.
019ea5e0-7dde-727b-9570-b784348720fb Here's how it actually works
The bottom line is that once it’s connected, you talk to your entire technical knowledge base using plain English.
First, subscribe to the Archbee MCP and provide your API key within Vinkius.
Second, tell your AI client exactly what you need done—for example, 'Sync this YAML file' or 'Create a new space called Billing Guides'.
The agent then executes the necessary commands directly against your documentation platform and reports the outcome.
Who is this actually for?
This MCP solves a massive headache for teams whose product documentation lives in multiple places. It's essential for the Technical Writer who needs version control across environments, the Developer who can update API docs without leaving their IDE, and the Product Manager who needs to instantly locate requirements buried deep in old guides.
Using this MCP, they manage document lifecycles by creating new spaces, updating existing documents using create_update_doc, and publishing finalized content to staging or production environments.
They sync OpenAPI definitions directly into the documentation structure via sync_openapi and use the MCP to quickly check if a guide is up-to-date with the latest API changes, calling info_openapi for details.
PMs can query the entire knowledge base using search_docs to gather requirements from various sources, or retrieve specific content of an old requirement document using get_doc.
What Changes When You Connect
Search everything instantly. Instead of manually checking five different sections, you can use search_docs to query your entire organization's knowledge base for technical answers in seconds.
Keep API specs current without developer effort. By calling sync_openapi, you automatically connect structured OpenAPI files directly into documentation trees, enabling 'Try It' features right where users read the guide.
Control content flow and structure. Need to organize your product guides? Use create_space_group or clone_space to maintain a consistent hierarchy without manual folder setup.
Maintain version control simply. If you make changes in draft form, use merge_suggestion to pull those updates into the official document, keeping everything clean and traceable.
Get content where it belongs. You can rapidly populate docs using import_content or upload files, eliminating the tedious copy-pasting process from Jira tickets or meeting notes.
See it in action
A PM needs to answer a niche customer question.
The PM asks their agent: 'Find all documentation related to billing rate changes.' The agent executes search_docs, retrieves the top three documents, and summarizes the necessary information from across different spaces.
A developer updates a core endpoint.
Instead of manually updating code examples in Markdown, the dev tells their agent: 'Sync this new OpenAPI spec to the Payments guide.' The MCP runs sync_openapi, ensuring the documentation is immediately accurate and functional.
A technical writer reorganizes old guides.
The writer asks the agent: 'I'm retiring the Legacy Auth space. Please delete that whole area, but first, create a group called Deprecated Guides to hold its contents.' They use delete_space followed by create_space_group.
An onboarding flow needs multiple steps.
The agent is tasked with: 'Create a new space for Onboarding, clone the core setup guides into it, and add the latest markdown content about SSO.' This sequence uses create_space, clone_space, and import_content.
The honest tradeoffs
Trying to update docs manually.
Copying a new API field from the developer's chat window and pasting it into an old guide, then having to search for the right place to put it.
Use sync_openapi. Your AI client sends the structured definition directly via sync_openapi, updating both the content and any associated testing features automatically.
Losing track of documentation structure.
Having to manually click through dozens of folders to find a single piece of information because the organization has grown too big.
Use search_docs. Tell your agent exactly what you're looking for, and it queries every document in the entire knowledge base.
Overwriting critical content by accident.
A developer overwrites a key section of documentation because they didn't know if their changes were approved or just suggestions.
Use merge_suggestion. This tool ensures that suggested drafts are reviewed and deliberately merged into the primary, live version of the document.
When It Fits, When It Doesn't
You should use this MCP if your documentation is structured knowledge—meaning it has defined spaces, API definitions (OpenAPI), and requires global searching across multiple related guides. It's perfect for large engineering teams or companies with complex product lines. Don’t use it if your primary need is simple messaging communication or managing basic user profiles; those are better handled by dedicated chat or CRM connectors. If you only ever want to read documents, a basic getter tool would suffice. But because this MCP lets you manage the structure (via create_space), update content (via create_update_doc), and sync technical definitions (via sync_openapi), it handles the full documentation lifecycle.
Questions you might have
How do I search my docs with Archbee MCP? +
You use the search_docs tool to query all content across your entire organization. This lets you find specific technical details even if they are spread across multiple unconnected spaces.
Can I update API documentation using Archbee MCP? +
Yes, absolutely. You use sync_openapi to connect an OpenAPI definition directly to a document tree. This keeps your guides accurate when the underlying APIs change.
What if I need to delete a whole section of documentation? +
You can permanently wipe out an entire area using delete_space, or remove a group of related areas with delete_space_group. Be careful; this action is irreversible.
Does Archbee MCP help me organize my guides? +
It does. You can use create_space_group to gather multiple, related spaces into one logical container for easier navigation and structure management.
How do I add new content quickly using Archbee MCP? +
You use import_content when you have raw Markdown text. This tool inserts the provided content directly into your documentation structure without manual file uploads.
We've already built the connector for Archbee. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 19 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.