# Slite MCP > Slite connects your agent directly to your team's documentation and knowledge base. Ask questions about internal specs, review project notes, or update guides without logging into Slite. This MCP lets you treat your entire workspace like a searchable database accessed through natural conversation. ## Overview - **Category:** knowledge-management - **Price:** Free - **Tags:** documentation, wiki, search-indexing, ai-insights, content-verification, team-collaboration ## Description Slite helps teams stop wasting time hunting down facts buried in old documents. Instead of searching document titles and wading through search results, you just ask questions about your company's knowledge base, and the AI pulls out the specific answers. You can manage documentation quality too; if a policy is outdated or needs review, you flag it directly from your chat interface. This means product managers get accurate specs instantly, and ops teams keep the internal wiki current without manual overhead. Vinkius makes this easy: connect your preferred agent once, and you gain access to Slite's full documentation management tools, turning static content into immediate, actionable knowledge. ## Tools ### ask_slite_ai Ask the AI directly questions about your knowledge base documentation. ### create_note Generates a brand new note in your Slite workspace. ### flag_outdated Marks an existing document so that it gets flagged for required review. ### get_me Retrieves the profile details of the current user. ### get_note Grabs all the content and details for a single, specific note. ### list_note_children Lists all sub-notes that fall under one parent document. ### list_collections Retrieves a list of all structured knowledge collections available in your workspace. ### list_notes Gets a summary list of every note stored across the entire workspace. ### list_users Lists all user accounts associated with your organization in Slite. ### search_notes Performs a targeted search across multiple notes within your workspace using keywords. ### update_note Changes the content and metadata of an already existing note. ### verify_note Formally marks a document as accurate, signaling that it has been reviewed and approved. ## Prompt Examples **Prompt:** ``` Search for notes about the 'Marketing Plan' in Slite. ``` **Response:** ``` I've found 2 notes: 1. Marketing Plan 2026 (ID: n1), 2. Q3 Ad Strategy (ID: n2). ``` **Prompt:** ``` Show me the most active knowledge base documents this month with view counts and contributors. ``` **Response:** ``` Top 10 documents by activity. #1: "API Documentation v3" (456 views, 12 edits, 5 contributors). #2: "Onboarding Guide 2025" (345 views, 8 edits). #3: "Architecture Decision Records" (234 views, 15 edits, most collaborative). #4: "Sprint Planning Template" (198 views). #5: "Security Policies" (167 views, 3 edits). Total docs: 234. New this month: 18. Updated: 45. Stale (90+ days no edit): 67. Search queries: 890. Most searched: "API authentication" (34 searches). Knowledge coverage score: 78%. ``` **Prompt:** ``` Search the knowledge base for all documents related to API authentication and rate limiting. ``` **Response:** ``` Found 8 documents matching "API authentication" and "rate limiting". Most relevant: "API Authentication Guide" (last updated 3 days ago, OAuth 2.0, API keys, JWT tokens covered). "Rate Limiting Policy" (updated last week, 1000 req/min default, burst handling). "API Security Best Practices" (comprehensive, 2,340 words). "Developer Quickstart" (getting started with auth). "Troubleshooting Auth Errors" (common 401/403 fixes). 3 additional related docs. Combined reading time: 45 minutes. 2 documents flagged as needing review. ``` ## Capabilities ### Ask AI questions against docs You can ask natural language questions about your entire document library and get answers derived directly from the source material. ### Create or edit notes Generate entirely new meeting notes, project specifications, or knowledge articles right within your workflow. ### Track document status Mark documents as verified for accuracy, or flag content that needs an owner to review it before publication. ### Search across the workspace Find specific notes and collections by keyword, even if they are nested deep inside a hierarchy. ### Manage user accounts List all users in the organization to confirm who has access to which parts of the knowledge base. ## Use Cases ### Onboarding a new team member A manager needs to create an onboarding guide. Instead of copy-pasting from five different sources, they ask their agent via `ask_slite_ai` about 'API authentication requirements' and compile the definitive answer instantly. ### Updating a product spec A PM finds an old specification document. They use `get_note` to pull the current content, make necessary changes using `update_note`, and then run `verify_note` so the whole team knows it's accurate. ### Finding compliance rules A legal team member needs to know which internal documents cover GDPR. They use `search_notes` for 'GDPR' and then check the results, using their agent to summarize the key takeaways from all matching content. ### Auditing documentation status An ops team leader wants to know which guides haven't been touched in six months. They list collections (`list_collections`) and then use `flag_outdated` on any collection that looks stale, prioritizing updates. ## Benefits - Stop manually searching for facts. By using `ask_slite_ai`, you get immediate answers derived from your company's entire documentation, cutting research time by hours. - Maintain quality control across your docs. When a policy changes or a feature is deprecated, use `flag_outdated` to automatically trigger the review process before anyone uses old info. - Build content fast. Instead of opening Slite and starting from scratch, you can run `create_note` through your agent right where you are working, saving clicks. - Understand your knowledge structure. Tools like `list_collections` or `list_notes` let you map out exactly how your information is organized without leaving your chat window. - Trust the data source. When a document is accurate and approved, use `verify_note`. This action creates an auditable record that the content has passed review. ## How It Works The bottom line is, you get conversational access to all of your company’s structured documentation and notes. 1. First, get your API Key from your Slite workspace settings under Developer. 2. Next, paste those credentials into the Vinkius platform to establish the connection. 3. Finally, start chatting with your agent. You'll use natural language to ask questions or tell it to perform actions on your team's knowledge. ## Frequently Asked Questions **How do I use the `ask_slite_ai` tool with Slite MCP?** You simply type your question in natural language into your agent chat. The agent then queries the entire knowledge base and responds with an answer synthesized from those documents. **Can I use Slite MCP to update old documentation?** Yes, you can run `update_note` after retrieving content using `get_note`. This lets your agent modify existing notes and keep them current. **Does the Slite MCP help me prove a document is correct?** The tool `verify_note` allows you to formally mark a document as verified. This action confirms that the content has been reviewed and meets accuracy standards for your team. **What if I want to find notes from a specific project group?** You can use `list_collections` first to see how your data is structured, then use `search_notes` with keywords related to that collection for better results. **Is the Slite MCP only good for reading documentation?** No. You can also generate content using `create_note`, which lets you write and store new knowledge directly through your agent workflow.