Tettra MCP. Access internal wikis and Q&A from your IDE.

The Tettra MCP Server hooks your company's internal knowledge base directly into your AI client. This ain't just another search bar; it lets your agent actually do stuff with your wiki, making it a functional part of your developer workflow. You can deep dive into guides and SOPs without ever leaving Cursor or Claude.

If you need an answer, you hit up search_pages. It runs a full-text sweep across every page in the entire Tettra knowledge base, pulling back up to five relevant articles that match your query. If you're looking for something specific and know the ID, you can use get_page_content. That tool pulls the whole shebang—the title and the complete Markdown or HTML body—so you get the full context of any single wiki page for review.

Need to map out what documentation exists? You got tools for that. You start big with list_categories, which spits out all the top-level buckets in your Tettra knowledge base. If a category has sub-sections, you use list_subcategories against a parent ID to see those nested levels. Then, if you know the main section and want to see every page listed under it, run list_pages_in_category.

To get details on any specific grouping—like its metadata or rules—you call get_category_details, feeding it just the category's ID.

When it comes to content creation and edits, the server gives you full control. If your team needs a brand-new guide published, you use create_wiki_page. You gotta provide three things for this: the title, the actual content, and the target ID where it's gonna live. If an article is already out there but needs tweaking—maybe the process changed or someone fixed a typo—you call update_wiki_page, giving it the page ID and the new fields you want to change.

Sometimes, the whole wiki needs maintenance. You can use suggest_new_page when your agent thinks the team should write an article on a certain topic; it drafts that suggestion for review. And once someone writes or updates something, if they verify it's current and solid, they mark it as up-to-date using verify_wiki_page.

For the Q&A side of things, it’s dead simple. If you got a question that needs an answer from the team, run create_qa_question, which posts it right into your internal Tettra Q&A system board. To see what's already been asked and tracked, just use list_qa_questions.

Basically, you can handle everything: you search deep, you pull the content, you build new guides with create_wiki_page, you update old ones with update_wiki_page, you organize the whole structure using the list tools, and you manage questions by posting or listing them. It keeps your entire knowledge base right where it needs to be: callable by your agent.