Introduction to Klaxoon MCP

Learn what Klaxoon MCP is, what you can do with it, and how permissions work when connecting an AI assistant to your Klaxoon whiteboards.

Use Klaxoon MCP to let an AI assistant read, organize, and update your Klaxoon whiteboards from any MCP-compatible client.

What Klaxoon MCP is

Klaxoon exposes a Model Context Protocol (MCP) server so your own AI assistant can work with Klaxoon whiteboards - read what is on the board and create or update content through tools - without you jumping back and forth to copy, paste, or re-explain context. The goal is simple: stay in flow in your assistant or IDE while boards remain the place where collaboration lives.

The Model Context Protocol (MCP) is an open standard that lets assistants call tools in a consistent way. In practice, that means your assistant can see what is on your boards and change it when your permissions allow it.

Before you start - Prerequisites

  • An MCP-compatible client (e.g. Claude, ChatGPT/Codex, Cursor, or any other tool that supports MCP).
  • A Klaxoon account with access to the whiteboards you want to use.

What you can do with Klaxoon MCP

  • Extract structured output from board content: Turn board content into task lists, action items, or summaries you can paste or reuse into email, spreadsheets, Jira, Wrike or other tools.
  • Prepare workshops: Start from plain text, an attached file, or context from another MCP server to scaffold sections, frames, prompts, and starter content on a whiteboard before the session.
  • Create diagrams: Use instructions alone or inputs such as a spreadsheet, a URL, or Mermaid (or similar) source to produce flows, maps, and other structured visuals on the board.
  • Get summaries and situational awareness: Ask for a concise view of one board or several boards so you can stay current without opening every sticky. These summaries are generated by the model from the content it can read.
  • Organize visuals at scale: Group and arrange items by topic, status, priority, assignee, and similar dimensions. This is especially useful after brainstorming, when you want to tighten structure with less manual drag-and-drop.

Authentication and permissions

Klaxoon MCP follows the same access rules as the Klaxoon product. Users can only read or modify boards and content they are already allowed to see or edit in Klaxoon.

When you connect the MCP server, the assistant acts within your Klaxoon permissions. If you cannot access a board in Klaxoon, the assistant cannot access it through MCP either.

Important considerations

  • Supported object types are limited: Klaxoon MCP interactions are limited to text objects, sticky notes, shapes, and connectors.
  • LLMs are non-deterministic: The same query may produce slightly different responses each time. This is normal AI behavior, not a bug in the integration.
  • Be specific in your queries: Include permalinks, project names, folder locations, or task details when you know them to get better results.
  • Refine your prompt if needed: If the first response is not quite right, add more context and try again.

Troubleshooting

Use this section to resolve common Klaxoon MCP connector, OAuth, and client configuration issues.

I don’t have access to the MCP connector or integration settings

  • Ask an organization administrator to verify whether Allow API access by Third Party applications is enabled in the organization configuration. If it is off, OAuth or API-backed MCP usage will be unavailable for the whole organization.
  • Check your network connection and any firewall or proxy that might block the MCP server or authentication endpoints.

“Invalid Redirect URI” (OAuth)

  • With Claude Code or Codex, configure the client to use the callback port supported by Klaxoon MCP: 56447. If the MCP client uses another port, the generated redirect URI will not match the registered one. Fix the port, then run authentication again.
  • With other MCP clients, create your own OAuth app and register the redirect URIs for that client when the client is not supported with a turnkey configuration. Follow the setup guide for that client.
  • Complete OAuth in the browser profile where you are signed in to the correct Klaxoon account.

Lost connection, authentication failure, or OAuth errors

  • Restart authentication by disconnecting the MCP connector, or removing the server, and connecting again using the assistant’s flow.
  • After OAuth or MCP configuration changes, remove the entire MCP entry and create it again instead of only editing it. Some clients cache the old configuration.

Privacy, terms, and support

Your privacy matters. See the Klaxoon Privacy Policy and Klaxoon Terms of Use for details on how data is handled and how the API may be used.

  • Review how Klaxoon handles data: Read the privacy policy and terms of use before connecting Klaxoon MCP to an AI assistant.
  • Data is protected in transit and at rest: Klaxoon states that it protects data with encryption in transit and at rest. See How are the data protected? for an overview.
  • Get help when you need it: Visit the Klaxoon Help Center or, from your Klaxoon account, click Need help? and then Start discussion to contact technical support directly.

See available tools

To review the exposed tools, parameters, and limits, refer to Available tools page.