CENTRUX

AI integration · Personal knowledge

Connect AI conversations to your personal wiki with MCP

A useful answer should still be available when you start the next task. Keep reusable conclusions in your Centrux wiki so an MCP-compatible AI tool can search, read and update them across conversations.

Save reusable knowledge, not entire conversations

Record a solution, the reason for a decision, or a procedure you expect to repeat. A short page with a clear title is easier to reuse than a transcript that mixes decisions with abandoned ideas.

Centrux organizes wiki pages into concepts, decisions, how-tos, references, facts and troubleshooting. Add useful tags and explicitly ask your AI tool to save the conclusion you want to keep.

Connect an MCP client

For Claude Code, Codex or Gemini CLI, copy the setup prompt from Settings and let your coding AI configure the connection. Including a new key is optional: use a trusted private AI session. Without a key, the AI guides local credential setup. Web chat connectors require separate registration.

For manual setup, use a client that supports remote MCP servers and authentication headers. Support varies by client.

  1. Sign in to Centrux and generate a connection key under AI connections · API keys in desktop Settings.
  2. Use https://centrux.kr/api/mcp as the server URL.
  3. Configure Authorization: Bearer YOUR_API_KEY as the authentication header. Keep the real key in the client’s secret settings, never in a wiki page or public URL.
  4. Actually ask the client to list projects or search the wiki to check the connection. A restart may be needed after registration.

Search before creating another page

Start with “Find our deployment procedure in the wiki.” After resolving a new issue, ask the tool to update that procedure with the verified steps. This keeps knowledge in a maintained page instead of spreading it across near-duplicates.

Centrux MCP supports wiki search, reading, updates and links between pages. Its upsert tool updates an existing page with the same title, making it useful for a knowledge base you intend to maintain.

Separate knowledge from work to be done

Save the reason for a decision in the wiki, then create a task for its next action. For example: “Add a deployment check to the development project with a checklist.” Tasks can include status, priority, notes and checklist items.

Use the personal wiki for knowledge that spans projects. For shared editing, use the project wiki in the app. Access follows personal ownership and the project’s sharing permissions.